Method and system for connecting and facilitating the machine-to-machine delivery of a gift that may or may not have monetary value

ABSTRACT

A computer-implemented method and system for facilitating a sending of a gift from a first machine to a second machine may include a processor of a computer server reviewing a first list of one or more names of people maintained in a computer database. The processor may review context information related to the one or more names to determine if a moment exists for sending a gift from a first machine to a second machine. Content providers may also request one or more gifts to be identified when a second machine is proximate to a content provider who may fulfill a gift.

RELATED APPLICATIONS STATEMENT

This patent application is related U.S. Non-Provisional patentapplication Ser. No. 15/464,229, filed on Mar. 20, 2017, entitled, “AMETHOD AND SYSTEM FOR CONNECTING AND FACILITATING THE MACHINE-TO-MACHINEDELIVERY OF A GIFT THAT MAY OR MAY NOT HAVE MONETARY VALUE.”

DESCRIPTION OF THE RELATED ART

Sending a gift today to a person may present many problems for both theGifter and the Receiver. For the Gifter, problems may includeidentifying intended Receiver, why to send a gift the Receiver, what thegift should be, when to send a gift, where to deliver a gift, and how todeliver a gift. And there have not been any Systems established thathelp the Gifter sending a gift remove these burdens. For the Receiver,problems may include knowing the best gift he or she would like toreceive, an optimal time the gift is delivered to the Receiver,remembering when the gift is received, as well as how to respond to theGifter to acknowledge receipt and to extend any gratitude to the Gifteras appropriate.

Stated more simply, giving and receiving gifts is often burdensome, forboth the Gifter and the Receiver, with hurdles that prevent thesuccessful exchange and delivery for both parties. And systems have notbeen established to solve problems for both the Gifter and Receiver.

There are innumerable complex methods available to send a gift today.Traditionally, this exchange is accomplished by the Gifter visiting aretail store where an element is purchased and then subsequentlydelivered physically by the Gifter directly to the Receiver. Morerecently, purchase and delivery options have expanded with theprevalence of the Internet.

Purchases can be made online and a Gifter may ship a gift directly tothe intended Receiver's home address. Furthermore, a similar exchangecan all occur online with an Gifter sending a digital gift, such as agift card, to a Receiver's digital address, such as an email address.

However, all gifting methods today, including traditional and the morerecent digital gifting solutions, often share the same core problems forboth the Gifter and the Receiver: none of the conventional methods solvethe aforementioned problems of who, why, what, when, where and how toachieve the sending of a gift. And none of the conventional technologiessolve many of the problems mentioned for the Receiver, includingknowledge of what the best gift is, optimal time a gift is delivered,remembering a gift is waiting to be redeemed, and how to acknowledge theGifter that the gift has been received.

What is needed is a method and system that aids both the Gifter andReceiver with the complex problems surrounding both the sending andreceiving of gifts, whether they be physical or digital, of monetaryvalue or not, and delivered in a retail store or delivered digitally.

SUMMARY OF THE DISCLOSURE

A computer-implemented method and system for facilitating a sending of agift from a first machine to a second machine may include a processor ofa computer server reviewing a first list of one or more names of peoplemaintained in a computer database. The processor of the computer servermay review context information related to the one or more names todetermine if a moment exists for sending a gift from a first machine toa second machine. Each of the one or more names being associated with arespective second machine.

The processor of the computer server automatically generating a secondlist of one or more names of people associated with a moment forreceiving a gift. The processor of the computer server may receive froma first machine a selection of at least one of the names on the secondlist who have been identified as associated with a moment for receivinga gift.

The processor of the computer server may determine one or more gifts foreach name that is selected from the second list based on at least one ofpreference information and context information stored in a computerdatabase. The computer server may store the one or more gifts in a thirdlist.

The processor of the computer server sends the third list to the firstmachine and receives from the first machine a selection of a gift fromthe third list. The processor of the computer server may contact acontent provider for arranging delivery of the gift to a second machineassociated with a name selected from the second list.

The processor of the computer server may send a message to the secondmachine that a gift is being sent to the second machine. The firstmachine and second machine may comprise portable computing devices thatare battery-powered hand-held devices. Specifically, the portablecomputing devices may comprise mobile telephones.

The computer server may also monitor on-line social media to determine amoment for sending a gift from the first machine to a second machine aswell as monitoring on-line social media to obtain feedback on thesystem.

According to another exemplary embodiment, a computer-implemented methodfor facilitating sending of a gift from a first machine to a secondmachine may include a content provider requesting the Moment Core toprovide one or more gifts that may be available for fulfillment by thecontent provider. According to this exemplary embodiment, thecomputer-implemented method may comprise a processor of a computerserver creating a gifts database of gifts associated with contacts ofthe first machine. The method may further include a processor of acomputer server identifying the gifts as available for searching and aprocessor of a computer server receiving from a computer communicationsnetwork a request for a gift to be sent to the second machine, therequest originating from a computer server of a content provider.

Next, a processor of a computer server may search and filter the giftsdatabase based on criteria that is part of the request for the gift. Aprocessor of a computer server may then determine if one or more giftsmatch the criteria based on the criteria. A processor of a computerserver may then change one or more gifts that match the criteria to areserved status.

A processor of a computer server may then transmit the one or more giftsthat match the criteria over a computer communications network to thecomputer server of the content provider. A processor of a computerserver may receive a message from the computer communications networkthat at least one gift that matches the criteria will be fulfilled andthen a processor of a computer server may transmit a message over thecomputer communications network to the first machine and the secondmachine that states that at least one gift that matches the criteria isbeing fulfilled.

The method may further include a processor of a computer serverdetermining a status of the one or more gifts that match the criteriathat were sent over the computer communications network based on one ormore rules. A processor of a computer server may then determine if thestatus of any of the one or more gifts matches one or more rules. Aprocessor of a computer server may change a reserved status for a giftin the gifts database to an available status if the gift matches one ormore rules.

This summary is provided to introduce a selection of concepts that arefurther described below in the detailed description. This summary is notintended to identify key or essential features of the claimed subjectmatter, nor is it intended to be used as an aid in limiting the scope ofthe claimed subject matter.

BRIEF DESCRIPTION OF THE DRAWINGS

In the Figures, like reference numerals refer to like parts throughoutthe various views unless otherwise indicated. For reference numeralswith letter character designations such as “102A” or “102B”, the lettercharacter designations may differentiate two like parts or elementspresent in the same Figure. Letter character designations for referencenumerals may be omitted when it is intended that a reference numeral toencompass all parts having the same reference numeral in all Figures.

FIG. 1 is functional block diagram of an exemplary system for sendinggifts that includes dynamic components designed to capture a Gifter'sinformation and request, interactions with a merchant or deliverymechanism, and delivery of the intended element or service to theintended Receiver according to one exemplary embodiment;

FIG. 2 is a logic flow diagram illustrating an exemplary method for newuser registration and unregistered Receiver User registration accordingto one exemplary embodiment;

FIG. 3 is a logic flow diagram illustrating an exemplary method for giftrecommendation and executing gift redemption according to one exemplaryembodiment;

FIG. 4 is a logic flow diagram illustrating an exemplary method of theNotification System of FIG. 1 determines how to notify a Receiver of aPending Gift according to one exemplary embodiment;

FIG. 5 is a logic flow diagram illustrating an exemplary method forproviding Receiver Notification at the point of sale/transaction, upongeo-location, on-line, or by self-identification according to oneexemplary embodiment;

FIG. 6 is a logic flow diagram illustrating an exemplary method of howthe Insights Engine of FIG. 1 determines best redemption option forFulfillment System according to one exemplary embodiment;

FIGS. 7A-7G are exemplary screen shots of a portable computing devicerunning software that illustrates the collection of gift data tofacilitate the sending of an element by a Gifter according to exemplaryembodiments;

FIGS. 8A-8C are exemplary screen shots of a portable computing devicerunning software that facilitates the receipt of an element for aReceiver and enables optional feed back to the Gifter according toexemplary embodiments;

FIGS. 9A-9B are exemplary screen shots of a portable computing devicerunning software that include Push Notifications according to exemplaryembodiments;

FIGS. 10A-10B are exemplary screen shots of a portable computing devicerunning software that maps User interactions according to exemplaryembodiments;

FIGS. 11A-11C are exemplary screen shots of a portable computing devicerunning software that uses emojis and receiver redemption according toexemplary embodiments;

FIG. 12 is an exemplary table illustrating User Sentiment Scoresaccording to one exemplary embodiment;

FIG. 13 illustrates an exemplary computers and/or computer architectureaccording to one exemplary embodiment; and

FIG. 14 illustrates an exemplary portable computing device (PCD)according to one exemplary embodiment.

FIG. 15 is a logic flow diagram illustrating an exemplary method forfacilitating sending of a gift from a first machine to a second machine,in which a request for a gift originates from a content provider.

FIG. 16 is an exemplary screen shot of a portable computing devicerunning software that illustrates a gift/moment complete/fulfilledmessage to a receiver device based on a gift request/moment originatingfrom a content provider.

DETAILED DESCRIPTION

The term “exemplary” is used herein to mean “serving as an example,instance, or illustration.” Any aspect described herein as “exemplary”is not necessarily to be construed as preferred or advantageous overother aspects.

In this description, the term “application” may also include fileshaving executable content, such as: object code, scripts, byte code,markup language files, and patches. In addition, an “application”referred to herein, may also include files that are not executable innature, such as documents that may need to be opened or other data filesthat need to be accessed.

The term “content” may also include files having executable content,such as: object code, scripts, byte code, markup language files, andpatches. In addition, “content” referred to herein, may also includefiles that are not executable in nature, such as documents that may needto be opened or other data files that need to be accessed.

As used in this description, the terms “component,” “database,”“module,” “system,” “engine”, and the like are intended to refer to acomputer-related entity, either hardware, firmware, a combination ofhardware and software, software, or software in execution. For example,a component may be, but is not limited to being, a process running on aprocessor, a processor, an object, an executable, a thread of execution,a program, and/or a computer.

By way of illustration, both an application running on a computingdevice and the computing device may be a component. One or morecomponents may reside within a process and/or thread of execution, and acomponent may be localized on one computer and/or distributed betweentwo or more computers. In addition, these components may execute fromvarious computer readable media having various data structures storedthereon. The components may communicate by way of local and/or remoteprocesses such as in accordance with a signal having one or more datapackets (e.g., data from one component interacting with anothercomponent in a local system, distributed system, and/or across a networksuch as the Internet with other systems by way of the signal).

Referring now to the drawings, wherein the showings are for purposes ofillustrating certain exemplary embodiments of the present disclosureonly, and not for purposes of limiting the same, FIG. 1 is functionalblock diagram of an exemplary system 100 for sending gifts that includesdynamic components. These dynamic components of system 100 are designedto capture a Gifter's information and request, interactions with amerchant or delivery mechanism (i.e. fulfillment system 160), anddelivery of the intended element or service to the intended Receiver 106according to one exemplary embodiment.

Moment Core 101 may comprise at least one of computer software,hardware, or both and/or firmware, that store and filter information forfacilitating the creation and delivery of a gift. Moment Core 101 mayrun/be executed by a computer server 99.

Moment Core 111 may communicate with other software or hardware over viaan Application Program Interface (API 103) and via a communicationsnetwork 111. The communications network 111 may comprise a wide areanetwork (“WAN”), the plain-old-telephone-system (“POTS”), a local areanetwork (“LAN”), the Internet, or any combination of these and othertypes of networks. Through the network 111, the server 99 maycommunicate with the client devices 104, 105, 106 and the other servers130, 140, 109, 160, 170, etc.

Each of the computer servers described herein as well the client devices104-106 may support various submethods/routines which are part of alarger method for facilitating the transfer of a gift from a firstmachine 104 to a second machine 106. In a particular aspect, one or moreof the method steps described herein may be implemented by executableinstructions and parameters, stored in the memory 1208, 112 (See FIGS.13-14 ) and databases 109, 141, etc. that may form software embodimentsof the gifting system 100. These instructions that form the giftingsystem may be executed by the CPUs 1206, 1324 (See FIGS. 13-14 ) or anyother processor. Further, the processors, 1206, 1324, the memory 1208,112, the instructions stored therein, or a combination thereof may serveas a means for performing one or more of the method steps describedherein.

Many of the software elements illustrated in FIG. 1 may include anapplication programming interface (API) 103 and related components asunderstood by one ordinary skill in the art. As illustrated in FIG. 1 ,a “Gifter” 104 is a first machine, like a first mobile phone, of system100 that initiates an action, running the moment application software107 that is coupled to the server 99 across the communications network.The action of the Gifter/User 104 may be directed toward another secondmachine that may comprise a portable computing device, such as a secondmobile phone, designated as a “Receiver” 106. This second mobile phone106 may also run the moment application software 107 which is coupled tothe server 99 across a communications network 99.

The terms Gifter 104 and Receiver/Receiver 106 will be referenced fromthis point forward and will correspond to machines—and specifically theportable computing devices, like mobile phones, were the first phone 104sends a gift to the second phone 106. A machine, like a portablecomputing device 105 not running the moment application software 107will be referenced as a generic user 105 of the system 100.

As illustrated in FIG. 1 , a user 105 is a known member of the system100, though it is a device which is not in an active state of sending orreceiving a gift. A User 105 of the system 100 may be required to beregistered in order to use the system 100 as intended, though may alsoexist as an unregistered, but recognized member by the system 100 withsome unique identifier (such as, but not limited to, an email address orphone number). Registration and User identification for the system 100is covered more extensively in connection with FIG. 2 described below.

The gifter portable computing device “PCD” 104 and receiver PCD 106 bothmay comprise a wireless, mobile telephone (such as an Apple iPhone orSamsung Galaxy phone) or other digital communication device (such as anApple iPad or Dell desktop computer). The Gifter 104 and Receiver 106may communicate with Moment Core 101 over a wired network or wirelessnetwork 111 (such as, but not limited to, a local area network [LAN] ormobile telephone network).

A User device 105 may access the system 100 through a Moment Application(App) program 107, which serves as a specific platform for the User tointeract with the system 100 (common examples found through Apple AppStore and Google Android Apps). Alternatively, a User device 105, if thedevice 105 comprises a desktop computer or laptop computer [See FIG. 13], may access the system 100 via Moment Open application software 108via a platform able to access and perform operations on the Internetlike common web browsers (such as Safari and Chrome); by other platformsor programs with access to the mobile web (such as Google Mail andSlack); or via plug-ins to other platforms or programs (such as GoogleMail, Apple iMessage and Salesforce Enterprise App).

Both Moment App 107 and Moment Open 108 are considered as validplatforms for supporting the functions and features of the system 100.Additionally, Moment Core 101, and its various components, have theability to communicate over the communications network 111 with othercomputer servers, such as a server running an insights engine 140, aserver running a notifications system 130, and a server supporting acontent provider 109.

Content Provider 109 may comprise a computer server that serves MomentCore 101 by providing the source for a good or service that aFulfillment System 160 leverages to transfer from Gifter 104 to Receiver106 as a gift. Content Providers 109 may comprise computer servers ofretailers (like Macy's, Amazon, Home Improvement Stores like The HomeDepot and Lowes, etc.), computer servers of service providers (likeMerry Maids home cleaning), computer servers supporting digital media(like Netflix), and servers that may support other digital resources(like an emoji platform that serves pictographs).

The Insights Engine 140 may comprise a computer server running softwarethat filters user 105 information accessed by Moment Core 101 fromacross the communications network 111. This saved user information maycomprise a User Profile 141 accessed and created by the insights engine140. The User Profile 141 may function as a repository of attributes fora given User and accessed by the Moment Core 101 and its components asthey carry out operations. A User 105 may create a single verifiedidentity via a unique User Profile 141 stored by Insights Engine 140,which provides Moment Core 101 and its components information on Usersfor use by the System.

The User Profile 141 may include: Contacts data 142 (like savedcontacts—names, phone numbers, physical addresses, and e-mail addresseson a User's PCD or contacts from a User's email platform, like MicrosoftOutlook); Communication Systems Data 143 (like SMS texts through AppleiMessage, conversations through Facebook Messenger, among any other dataa user makes available from other communication platforms they may use);User Financial Data 144 (such as a bank account info and/or credit cardaccounts); Calendars 145 (like Google Calendar and Microsoft's SunriseCalendar); Social Data 146 from social media accounts (like Facebookaccount info including running feeds from Facebook accounts and Twitteraccount info and running feeds from the Twitter account); otherAddresses 147 (which may include digital User addresses like a MySpaceor Facebook pages), Location 148 of the PCD running the moment app 107(which may be acquired by the moment app 107 via Geo-Location 134 or bya User self-reporting their location); Personally IdentifiableInformation (PII) 149 (which may include sensitive attributes for aparticular User, such as a social security number or driver's licensenumber); other self-inputted User Input Data 1411 (such as personalgifting preferences like preferred dollar amount to spend, favoritefriends or preferred gifting occasions); or User Sentiment Score 1412(which is a summation of positive and negative activity by a particularUser of the system 100).

The Insights Engine 140 may continuously monitor and filter additionalinformation like News and Pop Culture 1401 (such as a world event likethe Olympics, a National event like the NFL Super Bowl, or a local eventlike a county fair); Date and Time 1402, among other data inputs theSystem may have access to. This information from the Insights Engine 140may determine how the system 100 interacts with a gifter 104 andreceiver 106. The Insights Engine 140 may inform the Moment Core 101 toactivate the Notification System 130, by which the System 100communicates information to a User.

The Notification System 130 may comprise a computer server runningsoftware that is accessed by Moment Core 101 across the communicationsnetwork 111 to facilitate the communication between the Gifter 104 andReceiver 106, other platforms and programs. The Notification System 130may communicate with one or more of the following systems: a point ofsale device 131 at a retailer; an e-commerce platform 132 like Amazon oreBay on-line stores; and a Reservation System 133 of a service providerlike an Airline, Hotel, or rental car.

The Notification system 130 may also access information such asGPS-based Geo-Location 134 of the Gifter 104 and/or the Receiver 106.The Point of Sale 131 device may be a physical, in-store component thataccepts and processes a transaction or may be online through aretailer's eCommerce Platform 132, or some not yet known means ofrecognizing and processing a customer's purchase. An eCommerce Platform132 is recognized as a retailer's digital store where a customer maydigitally interact with and purchase a retailer's goods. The ReservationSystem 133 may also include one or a number of platforms or programs,such as OpenTable's reservation platform; a specific restaurant, spa,recreational or fitness club reservation program; among other programsor platforms an individual may use to book and hold time with some otherentity. Geo-Location 134 refers to a specific technology use byNotification System 130 in which a Gifter 104 or a Receiver 106 hastheir location recognized by Moment Core 101 and in which that locationmerits a communication as determined by Notification System 130. TheSystem 101 may receive Geo-Location data from a number of technologieslike software installed in many smart phone devices, RFID radiotechnology, or some other location technology available to the system.

The Notification System 130 may also access a Feedback Loop 135. FeebackLoop 135 refers to the Notification System 130 providing communicationamong relevant Gifters 104/Receivers 106 for a given action executed byMoment Core 101. For instance, Notification System 130 may send theGifter 104 a communication that their Receiver 106 has received theirgift, essentially closing the loop on the communication for thatparticular action, which removes that burden from the Receiver 106.Notifications are direct communications or prompts sent to Gifters 104and/or Receivers 106 and may be sent by Notification System 130.

Referring now to the Gift System 150, the Gift System 150 receivesdirect inputs from the moment core 101 to facilitate the selection anddelivery of a gift from a Gifter 104 to a Receiver 106. A Pending Gift153 is an element a Gifter 104 has sent through the system to anotherReceiver 106, but that has not yet been received or redeemed by thatReceiver 106. Once the element is received or redeemed by Receiver 106,the Pending Gift 153 will be referred to as Redeemed Gift 154 to helpbetter communicate user flows and use cases.

Gift Defaults 151 may include gift options such as a dinner out, aspecific element like a baseball cap, a specific service like a homecleaning, a category such as “Spa Day” or some other gift description orgift type. Gift Defaults 151 may be dynamically presented by Moment Core101 based on information held by the Insights Engine 140 and may beinfluenced by a profile of Receiver 106 stored in user profiles 141

Gift Defaults 151 may comprise data such as tagged criteria, or GiftCriteria 152, that the Gift System 150 logs with the system 100 in orderto use in creating and delivering a Pending Gift 153. Gift Criteria 152may include data defined by the Fulfillment System 160 such as how agift is to be executed or may include data defined by Insights Engine140 that may associate specific gift types for specific times of theyear (like suggesting a package of chocolates around Valentine's Day) orother criteria saved to a User Profile 141. A Gifter 104 may also beable to self-enter criteria that will be used by Gift Criteria 152 todetermine Gift Defaults 151, and logged by Gift System 150 (likepreferences of price point or occasion for a User to send or receive agift) to User Profile 141. The Gift System 150 logs and records eventsassociated with a particular Pending Gift 153 that may originate fromthe Fulfillment System 160 on how and when the Notification System 130will be engaged/communicated with to alert the Receiver 106 of adelivery of his or her gift.

Referring now to the Fulfillment System 160, this system 160 isresponsible for executing a Pending Gift 153 to the Receiver 106. Theelements may originate from Content Providers 109, which may includePhysical stores 162 (brick and mortar stores like Macy's, The HomeDepot, Lowes, or a local bakery), Digital platforms 162 (like eCommercePlatforms 132 Gilt.com or Macy's.com), during an event Intercept 163(such as a musical concert venue or while dining out at a restaurant), aService Provider 164 (like Merry Maids home cleaning or delivery servicelike Uber or United Parcel Service), or through some other merchant orservice provider (such as an emoji platform that serves pictographs likesmiley faces).

Referring now to the Admin System 170, this system comprises a computerserver running software that communicates with and enables Moment Core101 to manage attributes of all other components of the system 100 (suchas Users 104, 105, 106, User Profiles 141, and Content Providers 109,etc). Reporting 171 is a sub-module/component of the Admin system whichmay provide output from the system 100 on these aforementionedcomponents to operating team of the system 100 to help manage Users andmeasure improvements for the system 101. Offers 172 may comprise asubcomponent/sub-module of the admin system 170 that communicates withMoment Core 101 to send offers/incentives to Users 105 to register withthe system 101 (like offering a free gift to send or a discount on aparticular gift) all of which may be tracked and managed directly byAdmin System 170.

Financial Institutions 180 may comprise banks and or credit cardproviders (such as Bank of America or a payment processor likeFirstData) and may communicate with Moment Core 101 across thecommunications network 111 in order for the Gifter 104 to providefinancial data 144 (part of profile 141) to be used to purchase a giftor the system 100 my send electronic invoices (i.e. via e-mail) directlywhen a good or service is exchanged from one entity to another, whetherit be between Users 105/Gifters 104/Receivers 106 or from the system 100to a User 105/Gifter 104/Receiver 106 or with a Content Provider 109.

The Moment Core 101 and server 99 may also be coupled to a database 175that may store one or more validated gift(s) created by Moment Core 101during method 300 of FIG. 3 described in further detail below.Validation of each gift within database 175 may include, but is notlimited to, soft-touch checks conducted by Moment Core 101(i.e.—validating email address or zip codes associated with receivingclient device 106) to deep validations where Moment Core 101 tries tointeract with the receiving client device 106 (i.e.—Send an email to thereceiving device 106 and expect an emailed response). These validatedgift(s) are stored in database 175 and may be used by Moment Core 101 tomatch against requests made by content providers 109 for available giftsas described in further detail below in connection with FIG. 15 .

Referring now to FIG. 2 , this figure is a logic flow diagramillustrating an exemplary method 200 for new user registration andunregistered Receiver User registration according to one exemplaryembodiment. A User 105 (which is a portable computing device 105 thatmay either comprise a mobile phone or laptop/desktop computer) mayregister with the system 100.

However, it should be noted that a User 105 may not have to register tobe known to the system 100 (instances of this are covered within). AUser 105 may access the system 100 over the communications network 111of FIG. 1 in block 202. The User 105 may provide some PersonallyIdentifiable Information “PII” to the system 100 as illustrated in block203, which is then saved by the moment core 101 to a User Profile 141.PII 149 may include, but is not limited to, financial accountinformation, like a bank account or a credit card (such as AmericanExpress, MasterCard, or Visa), a merchant loyalty account (such as agrocery store—Kroger Rewards or a pharmacy retailer store like CVSExtraCare Rewards Program), social media account (such as Facebook orTwitter), zip code, home address, biometrics (such as a fingerprint orretina scan) or some other means by which the System may use to uniquelyidentify the User.

This PII may be manually entered on the PCD by the User. Alternatively,the User may instead take an image of the information requested fromtheir PCD using their PCD camera 1275, 1348 (See FIGS. 13-14 ).

This information may also be used subsequently to charge the User 104for using the System as a Gifter, inform the Insights Engine 140 basedon User behavior, or to collect other information that may be used amongother data points collected by the System. Upon providing PII 149 inblock 203, in blocks 204 and 205, the Moment Core module 101 maydetermine whether the User 105 exists and has a User Profile 141. TheMoment Core module 101 may recognize a User with PII 149 provided afteranalyzing the existing records in the User Profile system 141 (see FIG.1 ).

The Moment Core module 101 may complete blocks 204 and 205 this bychecking against User Profile 141 logs. If the inquiry to decision block205 is positive, then the “Yes” branch may be followed by the MomentCore module 101 to block 215 in which the Moment Core module 101 maygenerate a log of this instance of interaction with the User 104. Atblock 215, the recognized User may not be required to take furtheraction with the system 100 and the method ends.

If the inquiry to decision block 205 is negative, then the Moment Coremodule 101 follows the “No” branch to block 206 in which the Moment Coremodule 101 may prompt that User to enter PII 149 in order to registerand use the system 100. Next, in decision block 207, the Moment Coremodule 101 determines if the User 105 has completed registration. If theinquiry to decision block 207 is negative, then the “No” branch isfollowed to block 215 in which the Moment Core module 101 records thatthe User's registration was started but is incomplete. The Moment Coremodule 101 saves the incomplete record in the User Profile system 101 inwhich the user 105 may log-in at a later time to complete registration.

If the inquiry to decision block 207 is positive, then the “Yes” branchis followed to block 208 in which the Moment Core module 101 identifiesthe user's credentials (received with the PII 149) as a registered user.Next, in decision block 209, the Moment Core module 101 determines ifthe user wants to send a gift to a receiver 106. If the inquiry todecision step 209 is negative, then the “No” branch is followed to block215 in which the Moment Core module 101 logs the registered user statusof the new potential gifter 104. The process then ends/stops.

If the inquiry to decision step 209 is positive, then the “Yes” branchis followed by the Moment Core module 101 to block 210 in which theMoment Core module 101 logs the identifying information for the receiverprovided by the Gifter 104. The process then continues to decision block211.

In decision block 211, the Moment Core module 101 will search all userprofiles stored in the User Profile system 141 to determine if theintended Receiver 106 is registered with the system 100. If intendedReceiver 106 has an existing profile in the User Profile system 141,then the “Yes” branch is followed to block 214 in which the Moment Coremodule 101 will confirm that the intended Receiver 106 is a recognizeduser. This status will then be logged by the Moment Core module 101 inthe User Profile 141 in block 215.

If the inquiry to decision block 211 is negative, then the “No” branchis followed by the Moment Core module 101 to block 212 in which theMoment Core module 101 may send a notice to the intended Receiver 106via the Notification System 130. This notification may be delivered bythe Notification System 101 to the intended Receiver 106 as an SMS,email, or by some other means in which it is able to alert User 106 thatthe Gifter 104 is trying to send the Receiver 106 a gift. Thatnotification may contain an invitation to the Receiver 106 tojoin/become a member of system 101.

In decision block 213, the Moment Core module 101 is determining if theintended Receiver 106 has downloaded one of the software applications[Moment App 107 or Moment Open 108] and plans to register with thesystem 100. If the inquiry to decision block 213 is positive, then theMoment Core module 101 follows the “Yes” branch to block 206 where theMoment Core module now manages the registration of the intended Receiver106.

If the inquiry to decision block 213 is negative, then the “No” branchis followed by the Moment Core module 101 to block 215 in which theMoment Core module 101 records the unregistered status of the intendedReceiver 106 and the process ends.

Referring now to FIG. 3 , this figure is a logic flow diagramillustrating an exemplary method 300 for gift recommendation andexecuting gift redemption according to one exemplary embodiment. Severalexemplary screen shots illustrated in FIGS. 9A-9B will be referencedduring this description of the exemplary method 300.

In block 299, a Gifter 104 will access the system 100 and send a messageto the Moment Core module 101. Alternatively, the Notification System130 will alert the Gifter 106 with a message “Z” in exemplary screenshot 1032 of FIG. 9B. Screen shot 1032 illustrates a calendar running onthe PCD of Gifter 104 and which is monitored for events by NotificationSystem 130. In the exemplary embodiment illustrated in FIG. 9B, theNotification System 130 identified a potential Receiver 106 of theGifter 104 based on a meeting that was scheduled in the calendar and inwhich the Receiver 106 was listed as one of the meeting participants.

Referring back to FIG. 3 , in block 301, the Gifter 104 may start theprocess of selecting a gift for a Receiver 106. Referring now to thescreen shot 1010 of FIG. 7A, this figure illustrates a screen that maybe presented when the Gifter 104 opens the moment app 107 running on amobile phone. When the Gifter 104 selects element ‘A’ of screen shot1010, which is a on-screen button with words “Send a Moment” on theSystem interface, the Gifter 104 may continue on to the next screen shot1011 of FIG. 7B.

FIG. 7B corresponds with block 302 of FIG. 3 . In block 302 and asillustrated in FIG. 7B, the Gifter 104 is presented with a list “B” ofcontacts that were automatically selected by the Moment Core module 101working with the Notification System 130 and the Profile System 141. Forexample, for potential Receiver 106 of Philip West, the Moment Coremodule 101 determined that this person was traveling a distance toattend a meeting with the Gifter 104. For the potential Receiver 106 ofBill Lamarr, the Moment Core module 101 determined that this person iscelebrating an anniversary in one calendar week.

Instead of the Gifter 104 deciding which potential Receiver 106 toselect, the Gifter may select option “C” of screen shot 1011 and let theMoment Core module 101 determine which contact of the Gifter 104 toselect as the intended Receiver 106 of a gift.

Referring back to FIG. 3 , in decision block 303, the Moment Core module101 determines if the Gifter 104 has selected a contact to be a Receiver106 such as one of the contacts as presented in the list of screen shot1011 of FIG. 7B. If the inquiry to decision block 303 is negative, thenthe “No” branch is followed to block 315 in which the Moment Core module101 captures the last Gifter interaction and saves it to the profilestored in the Profile System 141. The process then ends.

If the inquiry to decision block 303 is positive, then the “Yes” branchis followed by the Moment Core module 101 to block 304 in which theMoment Core module 101 records the selection of the contact as theintended Receiver 106 and then presents the Gifter 104 with potentialgifts for the intended Receiver 106 based on an analysis by the InsightsEngine 140.

During block 304, the Moment Core module 101 verifies if the intendedReceiver 106 has an existing profile in the Profile System 141. If theReceiver 106 is not a known member, the Moment Core module 101 via theNotification System 130 may send a notification to that individual (suchas through SMS and/or email) with instructions to become a member aspreviously noted above and illustrated in FIG. 2 . If the intendedReceiver is already a member of the system 100, no sign-up notificationis needed. The Insights Engine 140 determines Gift Defaults 151 topresent to Gifter 104, such as those illustrated in FIG. 7C which is ascreen shot 1012. Screen shot 1012 of FIG. 7C provides a list of GiftDefaults 151 for the contact of Philip which was selected by the Gifter104 in FIG. 7B.

The Insights Engine 140 after analyzing the profile for the Receiver 106of Philip in the Profiles System 101 determined that Philip desired thefollowing gifts: a baseball cap “E”, drinks, home cleaning services,dinner, a movie, or clothing as his preferred gifts. For baseball cap“E,” the Insights Engine 140 reviewed wishlists that the Receiver 106 ofPhilip maintained on one of his on-line store databases, such as Amazonbrand of on-line stores. The Receiver 106 of Philip had flagged thebaseball cap as a potential purchase that he might make in the future.

Referring back to FIG. 3 , next in block 305, the Moment Core module 101determines if a gift has been selected. If the inquiry to decision block306 is negative, then the “No” branch is followed to block 315 in whichthis action is recorded in the Gifter's profile. The process then ends.

If the inquiry to decision block is positive, then the “Yes” branch isfollowed to block 306 in which options for the monetary value of theselected gift are displayed by the Moment Core module 101. See FIG. 7Din which the “Drinks for Philip” option was selected from FIG. 7C. FIG.7D illustrates a screen shot 1013 that provides options G, H, I, J, andK for the Gifter 104 to select with respect to monetary value for adrink gift for Philip. Option G allows the Gifter 104 to select amonetary amount from a drop down menu. Option H allows the Gifter 104 toenter in a customized monetary value for the gift.

Option I of FIG. 7D allows the Gifter 104 to designate no limit on moneyfor this gift. Option J allows the Gifter 104 to let the Moment Coremodule 110 to decide on the monetary amount. And Option K allows theGifter 104 to select a range of monetary value such as up to ten U.S.dollars ($10 U.S. Currency) and up to fifteen U.S. dollars ($15 U.S.Currency). These amounts are exemplary only and other amounts may beused/employed as understood by one of ordinary skill in the art.

Referring back to FIG. 3 , next in decision block 307, the Moment Coremodule 307 determines if a monetary amount has been selected by theGifter 104. If the inquiry to decision block 306 is negative, then the“No” branch is followed to block 315 in which this action is recorded inthe profile of the Gifter 104. The process then ends.

If the inquiry to decision block 307 is positive, then the “Yes” branchis followed to block 308 in which the Moment Core module 101 presentsthe Gifter 104 with a list of delivery options, such as thoseillustrated in FIG. 7E.

In FIG. 7E, an exemplary screen shot 104 is illustrated which lists atleast three delivery options L, M, and N for the gift which was selectedin screen shot 1013 of FIG. 7D. These delivery options may include, butare not limited to, option L—“in the perfect moment” in which the MomentCore module 101 determines when the Receiver 106 plans to transmit moneythat may correspond with the gift 153 that was selected by the Gifter104. Option M may include “Immediately” where the Moment Core module 101may send a notice using the delivery system 130 to deliver the gift 153immediately and sent a note with the gift information to the Receiver106. Option N may allow the Moment Core module 101 to decide the right“time” or “moment” for delivery by monitoring activity of the Receiver106. The Moment Core module 101 using the insights engine 140 maydetermine timing for delivery of the gift 153 by reviewing contextinformation available to the insights engine.

Referring back to FIG. 3 , in decision block 309, the Moment Core module101 determines if the Gifter 104 has selected one of the gift deliveryoptions (L, M, or N of FIG. 7E). If the inquiry to decision block 309 isnegative, then the “No” branch is followed to block 315 in which thisaction is recorded in the profile of the Gifter 104. The process thenends.

If the inquiry to decision block 309 is positive, then the “Yes” branchis followed to block 310 in which the Moment Core module 101 capturesthe selected delivery option and provides confirmation of the selection,such as illustrated in FIG. 7F that includes screenshot 1015. Theinformation presented in screenshot 1015 is generated when the Gifter104 selects the “In the perfect moment” delivery option in screenshot1014 of FIG. 7E. If the Gifter 104 had selected the “immediately”delivery option in screenshot 1014 of FIG. 7E, then screenshot 1015would display “immediate delivery selected” message.

“In the perfect moment” screenshot 1015 of FIG. 7F allows the Gifter 104to select various options for the surprise delivery, such as, but notlimited to, the value of the gift, the location of the gift (i.e. whatparticular business—i.e. a bar for drinks), the date/day of the surprisedelivery, and even a time of day as desired. The Gifter 104 may alsoallow the Receiver 106 to keep any excess value of the gift—i.e.—for an“up to $10 drink gift” may allow the Receiver 106 to retain theremaining value should the Receiver 106 spend less than the allottedgift amount (i.e.—$6 was spent when $10 was allotted by Gifter 104).

In decision block 311, the Moment Core module 101 determines if theGifter has edited the surprise gift 153 details. If the inquiry todecision block 311 is negative, then the “No” branch is followed todecision block 313.

If the inquiry to decision block 311 is positive, then the “Yes” branchis followed to block 312 in which the Moment Core module 101 records anychanges/selections to screenshot 1015 of FIG. 7F. The process thencontinues decision block 313.

In decision block 313, the Moment Core module 101 confirms theselections made in screenshot 1015 of FIG. 7F. If the inquiry todecision block 313 is negative, then the “No” branch is followed inwhich the Gifter 106 has cancelled the gift 153 and the process thenends.

If the inquiry to decision block 313 is positive, then the “Yes” branchis followed to block 314 in which the Moment Core module 101 recordssends messages to the Fullfillment System 160 about the gift 153 andpresents the Gifter 104 with a “Gift success message” screenshot 1016 ofFIG. 7G.

Referring now to FIG. 4 , this figure is a logic flow diagramillustrating an exemplary method 400 on the Notification System of FIG.1 determining how to notify a Receiver 106 of a Pending Gift 153according to one exemplary embodiment. Block 299 is the first step inwhich the Moment Core module 101 recognizes there is a Pending Gift 153.Next, in decision block 401, the Moment Core module 101 checks InsightsEngine 140 for User Profiles 141 to determine whether Receiver 106 isknown to the system.

Should a Receiver 106 not be recognized by Moment Core 101 [the “No”branch from decision block 401], the un-recognized Receiver 106 may berequired to move through User registration as previously covered andillustrated in FIG. 2 as shown in block 409. In decision block 410, theMoment Core module 101 determines if the Receiver 106 provides therequested information for registering with the system 100. If theinquiry to decision step 410 is negative, then the “No” branch isfollowed to block 405 where the Fulfillment System 160 may determine thebest method to ensure that the intended gift is delivered to thatReceiver 106 based on the limited information that may have beenprovided in decision block 410. This is covered in more detail anddirectly referenced in the explanation for FIG. 5 .

Should Receiver 106 provide adequate information or should the MomentCore module 101 recognize Receiver 106, the “Yes” branch from decisionblock 410 is followed to decision block 402, where the Gift System 150confirms with whether Gifter 104 selected to deliver Pending Gift 153immediately.

Should Fulfillment System 160 detect that Pending Gift 153 is requiredto deliver immediately to Receiver 106 [the “Yes” branch from decisionblock 402], then the Notification System 130 may then send a notice toReceiver 106 (such as SMS or push notification) in block 407. In thisinstance, no additional System or Server check is required to determinehow Receiver 106 will be notified of the Pending Gift 153

Should the Fulfillment System 160 not have a command to deliverimmediately [the “No” branch from decision block 402], then it may checkto see if any input from Receiver 106 is required to fulfill PendingGift 153 as set forth in decision block 403. If no input is deemedrequired [the “No” branch exiting decision block 403], then theFulfillment System 160 may send a search request/inquiry to the InsightsEngine 140, which may include Receiver User Profile 141 as set forth inblock 404.

In at decision block 403, the Fulfillment System 160 determines it isrequired to ask for information from Receiver 106 [the “Yes” branchexiting decision block 403], then in block 411, the Notification System130 will prompt the Receiver 106 for required information (such asmailing address, office address, email, phone number, zip code,preferred shopping center, preferred merchants, or some other data thatmay be needed to deliver Pending Gift 153).

Receiver 106 in block 411 may be able to enter/input preferencesdirectly with Moment App 107 via their PCD, be able to send anelectronic communication back to Notification System 130 (such as SMStext or email), among other means to communicate the requiredinformation via Moment Open 108. Moreover, Receiver 106 in block 411 maybe able to enter his/her own request or preference directly on theirPCD, such as a mobile phone.

Next, in decision Block 412, the fulfillment system determines if theReceiver 106 has exceeded a predetermined time period for providing therequested information. This predetermined time period may be set by anadministrator of the system 100. Exemplary time periods would include,but are not limited, to five to ten minutes. If the Receiver 106 doesnot respond or fails to input required information at decision block412, then the “No” branch is followed to block 404, where theFulfillment System 160 may check the Insights Engine 140 for data tohelp determine the best delivery option.

For instance, the Insights Engine 140 may have an email address forReceiver 106 that would enable Fulfillment System 160 to send anotification via Notification System 130 about the delivery of theirPending Gift 153.

Delivery options and protocol will be explained in greater detailfollowing the description of FIG. 4 , since one main purpose of themethod 400 illustrated in FIG. 4 is providing a notification of PendingGift 153 to Receiver 106. FIGS. 5 and 6 described below contain specificdelivery scenarios for Fulfillment System 160.

In block 405 of FIG. 4 , Fulfillment System 160 checks availabledelivery options provided (and explained below in greater detail andillustrated in FIGS. 5 and 6 with specific scenarios for consideration).Next in block 406, the Fulfillment System 160 determines a “best” ormost ideal time to notify the Receiver 106 based on specific criteriaassociated with the Pending Gift 153 within Insights Engine 140, andGift System 150 [explained in greater detail below and illustrated inFIG. 5 with specific scenarios for consideration].

In block 407, upon filtering all available inputs, Notification System130 alerts Receiver 106 of the Pending Gift 153 and alerts Sender 104that Pending Gift 153 is now a Redeemed Gift 154 [explained in greaterdetail below and illustrated in FIG. 5 with specific scenarios forconsideration]. After block 407, the method 400 ends.

As one example for FIG. 4 , consider Gifter 104 selects to allow theMoment Core module 101 to determine delivery (as illustrated in FIG. 7E,screenshot 1014, element ‘N’ and block 403 ‘No’ path). Thisdetermination may happen when the Receiver 106 visits a retailercorresponding to Gift System 150 criteria and is identified by theMoment Core module 101. For instance, Receiver 106 may have a PendingGift 153 that is to be delivered at a women's department store. InsightsEngine 140 criteria would be accessed to determine if Receiver 106 haswomen's department store preferences logged. If Receiver 106, forinstance, previously indicated they do not like Macy's, the FulfillmentSystem 160 would eliminate Macy's as a Content Provider 109 option.

Alternatively, if Insights Engine 140 has a log that Receiver 106 lastredeemed at a particular women's department store (like Macy's), thenthat specific Content Provider 109 may be eliminated as an option toensure the Receiver 106 is served a unique Content Provider 109 fortheir next redemption experience. This input from Insights Engine 140and Content Provider 109, filtered by Fulfillment System 160, isexemplified in FIG. 4 , and specifically blocks 404, 405, and 406.Additional scenarios of Receiver 106 identification and redemption arecovered in detailed flows below and further exemplified in FIG. 5 .

Alternatively, a determination for notification may occur if Receiver106 engages in some other corresponding act to initiate the delivery ofthe Pending Gift 153 (like using their credit card or retailer loyaltycard known to the System) where the retailer corresponds to Gift System150 criteria, Insights Engine 140 criteria and input from ContentProvider 109 filtered by Fulfillment System 160 as exemplified in FIG. 4, and specifically in blocks 404, 405 and 406 of method 400. This latterdelivery method serves as an absolute and pure surprise in the moment ofa transaction and addresses the core problems associated with receivinga gift.

By a receiving a gift occurring in the moment of transaction, there isno effort the Receiver 106 must take to redeem or receive the giftintended for them as they had already initiated the purchase under theirown volition and with no prompt by the System. Furthermore, should thislatter method be enacted by the system 100, both the Gifter 104 and theReceiver 106 may be notified following the redemption via NotificationSystem 130 as exemplified in FIG. 8A, screenshot 1021 element ‘A’ and inFIG. 8C, screenshot 1023 element ‘Z’.

FIG. 8A illustrates a notification to the Receiver 106 and is based onthe prior example described in connection with FIG. 3 where the drinksgift for the Receiver 106 of Philip was selected. When the Receiver 106goes to pay for drinks with his PCD, then screenshot 1021 of FIG. 8A maybe presented. The Receiver 106 is also provided with the option to senda moment/gift 153 in response to receiving the current gift 154 asindicated by the screen button presented at the bottom of thepage/screenshot 1021.

FIG. 8C illustrates the notification provided to the Gifter 104 when thedrinks gift described in FIG. 8A and FIG. 3 is redeemed by the Receiver106 of Philip. The notification in screenshot 1023 congratulates theGifter 104 and explains which gift was transferred and who the Receiver106 of the gift is.

In view of FIGS. 8A & 8C, all problems attributed to receiving a gifthave been eliminated, including optimal time of delivery for theReceiver 106, having to remember a Pending Gift 153 is waiting [has notbeen sent], and closing the communication loop back to the Gifter.

FIG. 5 is a logic flow illustrating an exemplary method 500 forproviding Receiver Notification at the point of sale/transaction, upongeo-location, on-line, or by self-identification according to oneexemplary embodiment. Block 501 is the first step of method 500. In FIG.5 , methods and instances in which a Receiver 106 are notified and how aPending Gift 153 may be delivered are varied and determined by thevarious components of Moment Core module 101 as will be explained below.

The notification and delivery may occur at the same time or may beseparated in time. Notifications are determined by the Insights Engine140, Notification System 130, and Fulfillment System 160, all of whichgenerate inputs to Moment Core 101. Notification types vary based oninformation of the Receiver 106 gathered by Insights Engine 140, giftcriteria logged by Gift System 150 and available Content Providers 109logged by Fulfillment System 160.

Referencing FIG. 5 , in block 501, the Fulfillment System 160 firstrecognizes that a Receiver 106 has a Pending Gift 153 (i.e.—one that hasbeen selected for delivery by the Gifter 104 as described above). Inblock 502, the Moment Core module 101 then identifies the Receiver 106via data from the User Profiles system 141 with this identificationbeing directly related to the logic flow of FIG. 2 in which the system100 has taken previous action to identify Receiver 106.

The flow of FIG. 5 accounts for a known Receiver 106 to the system 100.Delivery to an unknown Receiver has been discussed previously. Should aReceiver 106 not be identified by Moment Core module 101 as a registeredUser 105 and should the Receiver 106 not subsequently register ifprompted via the Notification System 130, the Fulfillment System 160 mayuse other means to identify the Receiver 106 and deliver the intendedPending Gift 153.

This information about an unregistered Receiver 106 may include phonenumber, social media activity received from the Gifter 104, input by ahuman administrator of system 100, sending the Pending Gift 153 directlyto the Gifter 104 so the Gifter 104 may share it with their intendedReceiver 106, or some other means to ensure the Pending Gift 153 isdelivered.

Should no appropriate means exist to deliver Pending Gift 153 toReceiver 106, the Fulfillment System 160 may instead refund the purchaseor not charge Gifter 104, thereby removing the Pending Gift 153 for theintended Receiver 106. The Notification System 130 may then send anotification to Gifter 104 of this action, with all actions logged tothe profile stored in the User Profile system 141 for the Gifter 104.

Now, referring back to the logic flow of FIG. 5 , in decision block 503,the Fulfillment System 160 determines if a Content Provider 109 isavailable for Pending Gift 153 to an identified Receiver 106. ShouldFulfillment System 160 not identify an available Content Provider 109[the “No” branch exiting decision block 503], it will then determine notto notify a Receiver 106 in block 504. A Pending Gift 153 remainsattributed/assigned to that Receiver 106, awaiting the next instance theFulfillment System 160 may determine whether the Receiver 106 should benotified. The flow continues to decision block 521 described in furtherdetail below.

If the content provider is available [the “Yes” branch exiting decisionblock 503], the following decisions [decision blocks 506, 509, 511, 513,515, and 517] may be made/reviewed/processed in parallel by theFulfillment system 160. If anyone of inquiries to decision blocks 506,509, 511, 513, 515, and 517 is positive, then a respective “YES” branchis followed in response to that positive inquiry.

So, following the “Yes” branch from decision block 503 [meaning acontent provider is available for the pending Gift 153] to decisionblock 506, the Fulfillment system 160 in block 506 determines if theReceiver 106 has any known identifiable information available. If theinquiry to decision block 506 is negative, then the “No” branch isfollowed to decision block 509.

If the inquiry to decision block 506 is positive, then the “Yes” branchis followed to block 507. In block 507, the Fulfillment System 160 mayemploy Notification System 130 to send a notification with redemptioninstruction to Gifter 104 for that person to subsequently share withtheir intended Receiver 106. This scenario would indicate that InsightsEngine 140 holds no logs or information available to identify theReceiver. Next, in block 508, the Fulfillment System 160 would then logthe Pending Gift 153 as a Redeemed Gift 154 as indicated by block 508.The process then ends at this stage.

Referring back to decision block 503 of FIG. 5 , following the “Yes”branch from decision block 503 [meaning a content provider is availablefor the pending Gift 153]to decision block 509, the Fulfillment system160 determines in block 509 if the Receiver 106 has a known address(i.e.—mailing address, e-mail address, social media account, phonenumber, etc.) in the Profiles System 141. If the inquiry to decisionblock 509 is negative, then the “No” branch is followed to decisionblock 511.

If the inquiry to decision block 509 is positive, then the “Yes” branchis followed to block 510. In block 510, the Fulfillment System 160determines that the Receiver 106 should be notified. This address may bea physical, digital, or some other property by which Receiver 106 isable to receive some notification by Notification System 130, asdescribed above with respect to data stored in the User Profile system141. The method 500 then continues to block 520 which will be describedin further detail below.

Referring back to decision block 503 of FIG. 5 , following the “Yes”branch from decision block 503 [meaning a content provider is availablefor the pending Gift 153] to decision block 511, the Fulfillment system160 determines in block 511 if the Receiver 106 is located in a store(i.e. currently shopping). If the inquiry to decision block 511 isnegative, then the “No” branch is followed to decision block 513.

If the inquiry to decision block 511 is positive, then the “Yes” branchis followed to block 512. In block 512, the Receiver may be notifiedwith a printed receipt at the Point of Sale (POS) 131, through theReceiver's PCD, verbally by a store employee who receives an electronicmessage from the Fulfillment system 160, or some other means. The method500 then continues to block 520 which will be described in furtherdetail below.

Referring back to decision block 503 of FIG. 5 , following the “Yes”branch from decision block 503 [meaning a content provider is availablefor the pending Gift 153] to decision block 513, the Fulfillment system160 determines in block 513 if the Receiver 106 can be geo-located(potentially via Location data 148 of Receiver 106 filtered by theInsights Engine 140—i.e. with GPS signals from his/her PCD). If theinquiry to decision block 513 is negative, then the “No” branch isfollowed to decision block 515.

If the inquiry to decision block 513 is positive, then the “Yes” branchis followed to block 514. In block 514, the Fulfillment system 160 maysend an electronic message to the Receiver 106 (i.e. his/her PCD) and/orto a PCD of a store employee if the Receiver 106 is found to be locatedwithin a store. The method 500 then continues to block 520 described infurther detail below.

Referring back to decision block 503 of FIG. 5 , following the “Yes”branch from decision block 503 [meaning a content provider is availablefor the pending Gift 153] to decision block 515, the Fulfillment system160 determines in decision block 515 if the Receiver 106 is on-line,whether with a mobile phone or laptop/tablet PC—via a PCD. If theinquiry to decision block 515 is negative, then the “No” branch isfollowed to decision block 517.

If the inquiry to decision block 515 is positive, then the “Yes” branchis followed to block 516. In block 516, the Receiver 106 may be notifiedvia the Receiver's PCD or through an online pop-up window, among othermeans. The method 500 then continues to block 520 described in furtherdetail below.

Referring back to decision block 503 of FIG. 5 , following the “Yes”branch from decision block 503 [meaning a content provider is availablefor the pending Gift 153] to decision block 517, the Fulfillment system160 determines in decision block 517 if the Receiver 106 hasself-identified. A Receiver 106 may self-identify to the Moment Coremodule 101 (such as by texting the system 100 via SMS or alerting aContent Provider 109, a store employee, among other possible methods aReceiver 106 may take to identify/check-in with the system 100). If theinquiry to decision block 517 is negative, then the “No” branch isfollowed back to decision block 503.

If the inquiry to decision block 517 is positive, then the “Yes” branchis followed to block 518. In decision block 518, the Fulfillment System160 determines the optimal method of gift redemption, which may includepreviously mentioned methods of notification for Pending Gift 153. Themethod 500 continues to block 520.

In decision block 520, the Fulfillment System 160 determines if anyaction is needed from the Receiver 106 for the pending gift 153. If theinquiry to decision block 520 is negative, then the “No” branch isfollowed back decision block 522.

If the inquiry to decision block 520 is positive, then the “Yes” branchis followed to decision block 521. In decision block 521, theFulfillment System 160 determines if any action is needed from theReceiver 106 to receive notice of the pending gift 153. If the inquiryto decision block 521 is positive, then the “Yes” branch is followedback decision block 504 described above.

If the inquiry to decision block 521 is negative, then the “No” branchis followed to block 522. In block 522, the Fulfillment System 160 logsthe response of the Receiver 106 to the gift notification and determinesthe best delivery method. In block 523, the notification system 130alerts the Receiver 106 of the redeemed gift 154. In block 529, theFulfillment System 160 logs/records the receiver redemption and thennotifies the Receiver 106 and Gifter 104 of the redeemed Gift 154. Themethod 500 then ends.

The following are a few additional examples of Method 500 and how anotification may be triggered by Notification System 130 to a Receiver106. The Receiver 106 may be notified with the delivery of the gift at aContent Provider 109 (i.e.—like a store location) simultaneously as theyattempt to pay for their selected element with their credit card, whichmay be recognized via User Financial Data 144. In this instance, theNotification System 130 simultaneously notifies Receiver 106 of aPending Gift 153 while Fulfillment System 160 delivers the intendedPending Gift, as exemplified in blocks 520 (as no action is required bythe Receiver upon notification), 522 (the Fulfillment System 160 logsthe interaction and administers the Pending Gift 153) and 523 (Receiver106 is alerted of Redeemed Gift 154). This serves as an example of thepreviously mentioned Intercept 163 fulfillment method.

Referring again to FIG. 5 , the system 100 may send a notification viaNotification System 130 to the Receiver 106 alerting that there is agift in waiting, but withhold information on the type of gift (i.e.—thegift is for Fine Dining and this fact is not shared with the Receiver106). In this instance, Receiver 106 would receive the gift at the timedeemed best when they are within a recognized Fine Dining experience(i.e.—about to pay at a restaurant by providing credit card informationto the restaurant). A subsequent notification would then accompany thedelivery of the Redeemed Gift 154, as exemplified in block 523. Thisexample serves to explain instances in which a Receiver 106 may beidentified in-store or self-identify (such as sharing credit card infowith a restaurant), via geo-location, and on-line (like through theInsights Engine 140 referencing User Profile 141 data of a restaurantreservation made through OpenTable.com).

Following the notification of a Pending Gift 153 to Receiver 106, someaction may be required by the Receiver 106 (such as selecting apreferred Content Provider 109 or preferred delivery type viaFulfillment System 160) to have their gift delivered, as exemplified indecision block 520, following a positive inquiry (i.e.—the “Yes” branchfrom decision block 520).

At this point, the Fulfillment System 160 monitors whether any action orresponse is received from Receiver 106, as indicated with decision block521. Should no response be received by Notification System 130 [the “No”branch exiting decision block 521], then in block 504, the Pending Gift153 remains for Receiver 106 and would be filtered by Moment Core 101 atsome other time for notification and delivery in the future.

However, if the Receiver 106 does provide a required response that islogged by Notification System 130 [the “Yes” branch exiting decisionblock 521], then in block 522 Fulfillment System 160 then determines themethod for which the Pending Gift 153 is to be delivered.

As described above in connection with decision block 521, an action maybe required by Receiver 106 for the Gift System 150 to log a PendingGift 153 as a Redeemed Gift 154. The Gifter 104 may make thisrequirement for a Pending Gift 153. Should no confirmation be required[the “No” branch exiting decision block 521], the Notification System130 may alert Sender 104 and Receiver 106 of the Redeemed Gift 154status, which has been logged by the Moment Core 101 and informationsaved by Insights Engine 140 of both Sender and Receiver User Profiles141 for future reference, and exemplified in block 529.

At this stage, the Feedback Loop 135 mentioned in FIG. 1 has beenfulfilled. As illustrated in screen FIG. 8A, screenshot 1021, element‘A’ and in screenshot 1023 of FIG. 8C, element ‘Z.’ The NotificationSystem 130 may also prompt the Receiver 106 to alert the Gifter 104 thatthe gift has been redeemed or received. This alert may transpire on theReceiver's PCD 106 as a separate notification, or may accompany thegift, among other methods.

For instance, if a Receiver 106 is at a Fine Dining establishment andthe dinner is paid in full, the Receiver may be notified by an employeeof that dining establishment of the gift who may provide aself-addressed “thank you” card for the Receiver 106 to sign. This maysubsequently then be mailed by the establishment to the Gifter 104.Alternatively, the Receiver 106 may be able to respond through theNotification System 130 by SMS, video message captured by their PCD,pictograph emoji (like a smiley face), by sending a gift of their own,among other methods. The result of which is represented with FIG. 8B,screenshot 1022, element ‘N’ which is a photograph taken by the Receiver106 during the gift “moment.”

If the Receiver 106 is required to provide confirmation of receipt ofPending Gift 153 and does not do so during a time frame established bythe Fulfillment System 160, a subsequent notification may be issued viaNotification System 130. Otherwise, the Fulfillment System 160 maycontinue to monitor and determine another time to notify the Receiver,at which point a notification would be issued via Notification System130. Notifications remove the burden and risk from the Receiver 106 offorgetting they have a gift.

Referring now to FIG. 6 , this figure is a logic flow illustrating anexemplary method 600 of how the Insights Engine 140 of FIG. 1 determinesthe best redemption option for the Fulfillment System 160 according toone exemplary embodiment. In block 601, the Fulfillment System 160 logsall Content Providers 109 available to the system 100. In step 602, theInsights Engine 140 then filters Content Providers 109 based on selectcriteria (which may include User Profile 141, Date and Time 1402,Location 148, etc.) available to the Fulfillment System 160.

This output is then used by the Fulfillment System 160 in decision block603 to determine which Content Providers 109 are available for thespecific Pending Gift 153 redemption. If the inquiry to decision block603 is positive, then the “Yes” branch is followed to block 604. If theinquiry to decision block 603 is negative, then the “No” branch isfollowed back to block 601.

In block 604, the Notification System 130 may notify Content Providers109 of the Pending Gift 153 with a request in decision block 605 to optin to activate the Content Provider 109 for a Pending Gift redemption.Content Providers 109 may be always opted in to the Fulfillment System160, may place a bid on a particular gift redemption, or identifyinterest some other way such that the Content Provider is activated fora particular Pending Gift 153 redemption. If the inquiry to decisionblock 605 is negative, then the “No” branch is followed back to block601.

If Content Providers 109 are available and “opt-in” [the “Yes” branchexiting decision block 605], the the Fulfillment System 160 in block 606filters available and active (“opt-in”) Content Providers to a subsetthat may be presented to the Receiver 106. In this instance, theReceiver 106 may be sent a notification via Notification System 130 witha selection of a subset of Content Providers 109 to choose from in block607.

For instance, if Receiver Location 148 is known, the Fulfillment System160 may generate a subset and only provide the five closest ContentProviders 109 as options to select from. Additionally, should someContent Providers 109 be closed for the day at the time of this check,but others are shown to be open, then those that are open may bepresented as a subset of options regardless of their distance toReceiver 106.

If the Receiver 106 makes a selection, the Fulfillment System 160 wouldthen act to redeem the Receiver 106 Pending Gift 153 based on theirselection. Alternatively, Fulfillment System 160 may bypass the Receiver106 and pre-select a Content Provider 109 and notify the Receiverdirectly about the gift redemption as explained in connection with FIG.4 blocks 404, 405, 406 and 407 as previously described. A notificationis then sent to Receiver 106 via Notification System 130 when InsightsEngine 140 and Fulfillment System 160 determine the best time to sendthat notification in block 607 and previously commented above and alsodescribed in connection with block 406 of FIG. 4 . Additionally,Receiver 106 may be able to request a specific, yet unlisted, ContentProvider 109. At which point, the Moment Core module 101 would checkContent Provider 109 logs to determine whether that specific ContentProvider may serve as an option from which Receiver 106 may select.

Methods in which notifications may be delivered to the Receiver 106 arealso varied. Specific notifications have been mentioned previously, suchas SMS text message and email. However, there may be many other methods,including a web page pop-up, store employee verbal communication, aprinted notification at Content Provider 109 physical location, andphysical delivery of an element to an address, among many others. Thesemethods are not exhaustive and the Notification System 130 inconjunction with Fulfillment System 160 will determine the bestavailable notification method for a given gift.

Upon successful redemption of a gift, with that gift now referred to asRedeemed Gift 154, the system 100 has provided a benefit to the Receiver106 by solving the optimal time to receive their gift based on criteriathat optimizes the time and delivery method for that gift type, Location148, among other insights and information the Moment Core 101 and itscomponents take into account that have been covered within. TheNotification System 130 may help a Receiver 106 by reminding a gift iswaiting for them, reducing the burden of recall. Additionally,Notification System 130 may close the Feedback Loop 135 back to theGifter 104, removing the burden of determining an appropriate responseto the Gifter.

One specific method of identification and redemption covered has beenthe use of credit cards. In this instance, the Insights Engine 140retains a User 105 credit card information as User Financial Data 144,which may include a User 105 name, all logged to User Profile 141. Whenthe Receiver 106 uses their card during a transaction in which there isa Pending Gift 153, the Insights Engine 140 identifies that Receiver 106and Fulfillment System 160 can manage the delivery of the gift andnotification a number of ways. An example of type of transaction hasbeen referenced, like in Fine Dining. However, this could be anytransaction in which a credit card is used. For instance, a gift for“Grocery” would be associated with a purchase made at a supermarket(such as at Kroger or online with FreshDirect.com), or a gift for abaseball cap would be delivered when the Receiver 106 makes a creditcard payment at an associated retailer (such as J.Crew or mlb.com) witha recognized payment card logged by User Financial Data 144.

Payment and redemption of the gift may be managed a number of ways.These methods may include blocking the payment of the Receiver 106 atthe time of the transaction and instead billing the System directly, orby billing the Gifter 104 directly, all of which may be integrated withFinancial Institutions 180 (such as a bank like Bank of America or apayment processor like FirstData). Alternatively, the payment may bemade by the Receiver 106 and the Receiver 106 may be credited back thegift amount to a known credit card account (logged by User FinancialData 144) shortly after time of payment or at a later date via aFinancial Institution 180.

Payment by a Gifter 104 for use of Moment Network to deliver a gift to aReceiver 106 may occur a number of ways, including flat fee per giftsent, fee equating to a percentage of the value of the gift,subscription fee to access the System, unused amounts of a gift beingacquired, among other methods. For instance, payment may be provided bya participating Content Provider 109 engaged with the System (like CocaCola, or Kroger). A Content Provider 109 may have specific categoriesthat the Gifter 104 is able to select from and receive credits toward agift, full payment for a gift provided by the Content Provider, or someother promotional means that promotes the Gifter sending a gift throughthe System.

Insights Engine may track a User 105 and the gifts they send andreceive. This information may be incorporated with other available data(such as Facebook and Twitter activity) to generate User Sentiment Score1412 (as previously mentioned and exemplified in FIG. 10F), or karma,scoring. For instance, if a given User 105 actively sends one gift aweek to another User, their karma score may be higher than one thatsends one gift every month. Additionally, if two Users each send onegift a week, but one User is shown to have a higher positive sentimentscore through their social media activity, then this User may show ahigher karma score by the System.

Additionally, should one User 105 show to have a greater impact astracked by Insights Engine, their overall User Sentiment Score 1412 mayimprove. For instance, if one User 105 sends a gift and that single giftis tracked to show that multiple other Users sent a gift in reaction tothat User, then that first User may have a higher score logged to theirUser Profile 141. Scores may be used to provide credits to specificUsers, highlight User activity within the System by promoting specificUsers and their actions to other Users, among other methods toincentivize Users to engage with Moment Network.

Specific types of communication facilitated by Notification System 130from one User 105 to another User 105 have been commented previously,like the ability to send a “thank you” as represented in FIG. 8B,screenshot 1022, or screenshots 1021 and 1023 of FIGS. 8A & 8C thatrepresent the system 101 facilitating the sending of a gift. Screenshot1031 of FIG. 9A comprises notices A, B to the Gifter 104 from theReceiver 106 indicating the gift 154 has been redeemed and includessentiment from the Receiver 106.

These examples result in Notification System 130 ultimately deliveringsome form of notification on behalf of one User 105 to another User 105.These communications, as previously noted, may transpire over email,SMS, via a downloaded application to a User 105 PCD running programs 107& 108 of FIG. 1 , among other ways in which one individual is able tocommunicate with another individual, either established today or yet tobe known. One method of communicating information across many platformstoday is the use of pictographs, also commonly known as an emoji. Manyemoji carry a common meaning (like the common coffee cup image iscommonly known to represent a cup of coffee).

The Notification System 130 may use an emoji to convey information fromone User 105 to another. More specifically, Notification System 130 mayfacilitate the use of emoji in communications, an example of which isreflected in FIG. 11A, screenshot 1051. In screenshot 1051, a customkeyboard for selecting a unique emoji for a gift has taken the place ofa common keyboard on a User 105 PCD while they are using an emailplatform (like Google or Yahoo! Mail services). By using this keyboardto send an emoji, this individual may become a Gifter 104 where theperson that receives this emoji message then becomes a Receiver 106. TheGift System 150 logs this interaction and a Pending Gift 153 becomesactive. This example does not materially differentiate from previouslydescribed methods by which the system 100 operates, except that themethod by which the information is transferred from Gifter 104 to aReceiver 106 is being highlighted here as that of an emoji, orpictograph image.

FIG. 11B, screenshot 1052, element ‘D’ reflects an SMS communication inwhich an ice cream emoji has been entered in a message stream. This isto exemplify how an emoji is commonly understood to be shared today.This use of emoji may be sent through many platforms with an increasingnumber of platforms supporting image-based communication. Whatdifferentiates an emoji in this instance is that an emoji carried by theMoment Gift System 150 may become attached to an actual Pending Gift153, with all previously mentioned attributes for a Pending Gift 153holding true.

As an example, carrying the use of the coffee cup emoji forward,selecting this image may enable a Gifter 104 to send a Receiver 106 acup of coffee. Fulfillment System 160 would operate as previouslydescribed by checking available Content Provider(s) 109 and useNotification System 130 as described in detail earlier to notifyReceiver 106 of Pending Gift. So, sharing an emoji over a message thatMoment Core 101 has access to could result in the gifting from onefriend to another.

While some emoji are commonly used across many platforms, like thepreviously mentioned coffee cup, there also exist many custom emojiimages, such as the ice cream cone image represented by FIG. 11A,screenshot 1051, element ‘C.’ The Gift System 150 may use custom emojito deliver a specific element from a specific Content Provider 109. Forinstance, should a Gifter 104 select the custom ice cream emoji, thenReceiver 106 may be delivered an ice cream sundae from a specificContent Provider 109, like a ice cream retailer known as of this writingas Cold Stone Creamery. This emoji use could be for a single Cold StoneCreamery store location, all Cold Stone Creamery stores, or even allContent Provider 109, regardless of their product offering.

The process in which a Gifter 104 pays for this emoji transaction alsodoes not materially differ from what has been previously commentedwithin. For instance, the Fulfillment System 160 may charge the Gifter104 upon the Gift System 150 activating a Pending Gift 153, or may notcharge the Gifter 104 until Receiver 106 selects to redeem Pending Gift153, among other scenarios covered.

Related, the method by which any monetary component is transferredthrough an emoji transaction is not materially different than what hasbeen previously covered. For instance, the emoji may be attributed avalue and assigned a related gift card number with a held value or mayitself represent a known value at Content Provider 109 Point of Sale131, among other previously mentioned scenarios for assigning value to aPending Gift 153 and charging Gifter 104. Additionally, the emoji imageitself may contain a code or pattern by which a value is attributed.This code may be readable at a Content Provider POS.

Receiver 106 may be delivered an electronic notification of the selectedemoji, which is reflected in FIG. 11C, screenshot 1053. Here, the emoji,element ‘E,’ is accompanied by a redeemable gift code, element ‘F,’ andcorresponding redemption number, element ‘G,’ that could be used byContent Provider 109 to confirm this particular Pending Gift 153 whenReceiver 106 presents this information in a store. As previouslycommented, digital delivery of a Pending Gift 153 is not the only methodby which a Receiver 106 may receive a notification by NotificationSystem 130. All information could be sent, for instance, via mail to aphysical address, complete with a printed version of the elementscommented on screenshot 1053 of FIG. 11C.

Another alternative method for activating a Pending Gift 153 by GiftSystem 150 may act much like the aforementioned sharing of an emoji.However, instead of sending an emoji image, Gifter 104 may copy aspecific address of the system 101 (i.e.—a specific e-mail domain) in amessage to their intended Receiver 106 as represented in FIG. 11A,screenshot 1051, element ‘B.’ In this instance, Gifter 104 has copied aan email address of the gifting system 101 in an email. All remainingFulfillment System 160 activities that have been described above wouldthen remain in place for the fulfillment of this Pending Gift 153. Byincluding an e-mail address of the system 101 in an e-mail message,Gifter 104 circumvents use of a downloaded application to their PCD.

As previously mentioned and illustrated in FIG. 1 , the Moment Coremodule 101 may also comprise an Admin System 170, which enables theSystem to manage attributes of all other components of the System (suchas Users 105, User Profile 141, Content Providers 109, etc.). The AdminSystem 170 may manage incentives previously mentioned. These incentives,or Offers 172, could manifest a number of ways to encourage use ofMoment Network. For instance, the Admin System may establish a protocolto assign a Gifter 104 a nominal credit (which may be monetary ornon-monetary points that may be accrued to establish a monetary credit)to be used toward the purchase of a gift through the System.

The Admin System 170 may receive information via third-party platformsfor integrated marketing campaigns. For instance, a marketing programmay be run via Facebook or Twitter where Users receive credits withinthe System for performing some required action (such as “liking” thecompany Facebook page or sharing a Tweet or post). The Admin System 170may have an offers component 172 that would log those credits to a userstored the User Profile system 141. Subsequently, the Insight Engine 140and Gift System 150 would access this information in the User Profilesystem 141 should a User initiate sending a gift. Additionally, theAdmin System 170 may provide Reporting 171, which provides outputs suchas User 105 activity within the System.

User 105 activities may be tracked or traced to show the impact Users105 have on one another. This activity may be mapped by NotificationSystem 130 a number of ways, including the use of mapping tools to showlocation on a map (such as Google Maps or iOS Maps) where their giftsare being sent and received and surface the connection their gifts mayhave on other Users, as illustrated in FIGS. 10A-10B screenshots 1041and 1042.

For instance, one User 105 in Atlanta may send a gift to a User 105 inChicago and that friend may then send a gift of their own to anotherUser 105 in New York. Illustrated in screenshot 1041 of FIG. 10A,element ‘A’ illustrates a User, “Damon,” started this particular giftgiving cycle. Element ‘B’ indicated that “Damon” is the Gifter 104 andsent to a Receiver 106 named “Christie.” Element ‘C’ then illustratesthat “Christie” becomes a Gifter 104 as she sends a gift to a newReceiver 106 named “Daniel.” Notification System 130 may then map theconnection, showing how the initial gift impacted the larger communityand may do so regardless of whether all Users are known to one another,as illustrated with screenschot 1042 of FIG. 10B.

Here, element ‘D’ of FIG. 10B shows an anchor point, indicating theoriginating point with a dotted line to element ‘E,’ indicating aReceiver 106. The dotted line between element ‘E’ and element ‘F’indicates that the Receiver 106 associated with the point on the map aselement ‘E’ became a Gifter 104 to a new Receiver 106 represented byelement ‘F.’ Element ‘G’ then represents a total summation of theactivity first started by our initial Gifter 104 named “Damon” as we seenine gifts sent with a total of 2,345 miles traveled between points onthe map. Additional activity and data could be mapped in a similar way,like gifts sent to a particular Content Provider 109 or sent by aparticular Gifter 104, among other activates tracked and logged bycomponents of the system 100.

Now, following are a few examples of delivery scenarios to help clarifyflows and System functionality. For instances in which the Receiver 106is asked for input, the system 100 may give the choice of element orelement type for redemption to the Receiver 106.

In this case, the Receiver 106 may be presented with a selection poweredby Insights Engine 140, Gift System 150 and Fulfillment System 160 (like“dinner”, “shopping spree”, “Macy's”, or “Xbox One”) from which they mayindicate their gift preference that will in turn be logged by MomentCore 101 to User Profile 141. Additionally, the Fulfillment System 160may give the Receiver 106 the choice of time for redemption. In thiscase, the Receiver may be able to decide to have the gift redeemedimmediately (at which point the Gift System 150 would reveal the giftand instruction for redemption—covered in more detail below andexemplified in FIG. 5 ), allow the system 100 to determine the best time(in which case the Insights Engine 140 would prompt the NotificationSystem 160 to inform the Receiver 106 at a later time to redeem—coveredin more detail below and exemplified in FIG. 5 block 503), or somespecific day and time indicated by the Receiver 106.

Should a specific dollar value be given to Receiver 106 in a PendingGift 153, as illustrated in FIG. 7D, screenshot 1013 element ‘G’ and notfully used in the first transaction, that amount selected by the Gifter104 may carry over and remain on the Reciever's account to spend at alater time, may be carried forward to allow the Receiver 106 tosubsequently gift any unused amount to another Receive 106 of theirchoosing, may be acquired by the system 101, or some other action maytake place distributing the unused funds (such as being delivered to anon-profit charity).

For instance, if a Gifter 104 selects “Fine Dining” with an amountselected of “$100” though a Receiver 106 spends only $90 at a “FineDining” merchant, a $10 balance will remain. That $10 may be given tothe Receiver 106 in the form of a credit (as illustrated in FIG. 8B,screenshot 1021 element ‘B’) to spend on a future Receiver 106 of theirchoosing, which would help encourage the process of gift giving.

Alternatively, Fulfillment System 160 may only charge the Gifter 104 theninety dollars ($90) of the initial one-hundred dollar ($100) purchaseprice, effectively refunding the difference. Or charge Gifter 104 the$90 purchase price at the time of Redemption by Receiver 106 so norefund would be required.

The Fulfillment System 160 may use a variety of methods to deliver orredeem the selected Pending Gift 153 to the Receiver 106. TheFulfillment System 160 operates by incorporating Insights Engine 140input, Content Provider 109 information and Gift System 150 informationto determine the Pending Gift 153 method of redemption. These mayinclude delivery to the Receiver 106 physical or digital address (suchas their home, PO Box, email address, via the System on the User PCD, orSMS), through Geo-Location 134 (using technology such as geo-location,Bluetooth or RFID) possibly in conjunction with Receiver 106 Location148 at a physical retail store, accessing an eCommerce Platform 132website (through use of web cookies or User loyalty sign-in), byentering a store (for instance upon identification by a retailemployee), at time of checkout with the Point of Sale 131, using UserFinancial Data 144 to identify the credit card holder, among othermethods that are logged as preferred delivery options by Insights Engine140 for the Receiver 106.

For instance, should the Fulfillment System 160 leverage Geo-Locationtechnology like RFID, the Notification System 130 could log the Receiver106 Location 148 received and save that via User Profile 141 by MomentCore 101. This Location 148 could indicate that Receiver 106 is in aparticular store location (like a J.Crew) and the Notification System130 could alert that store location of the Receiver 106 and the PendingGift 153. At which point, the store staff could approach the Receiver106 and directly notify them of their Pending Gift 153. More referencesand examples of the Fulfillment System 160 flow follow below and areillustrated predominantly in FIG. 5 .

As shown in FIG. 1 , the Fulfillment System 160 recognizes general typesof gift redemptions, including Physical 161, Digital 162, Intercept 163,and Service 164. The many Physical 161 gift types refer to a redemptionin which a Receiver 106 has a tangible gift in hand upon redemption(which may be delivered directly to the Receiver, picked up in store, orsome other method to connect the Receiver with the Pending Gift 153). ADigital 162 gift type may include a digital code (like a gift card orpromotion code) that the Receiver 106 is able to use to receive aphysical good, or may solely exist as a digital gift (like an iTunesmusic subscription or online game points to Farmville). The Intercept163 gift type refers to the redemption in which a Receiver 106 paymentis superseded by a payment provided through the System, thus“intercepting” the Receiver's intended method of payment. The Receiveris prevented from purchasing a good or service because the Systemrecognizes their purchases matches a gift in waiting and instead chargesthe Gifter. The actual gift may result in either a Physical 161 orDigital 162 gift type.

For instance, an Intercept 163 gift type may occur when a Receiver 106goes to pay when in a store. Identification may occur at time of paymentby Financial Institution 180 as it registers use of a credit card withrecognized User Financial Data 144. Alternatively, the FulfillmentSystem 160 may interact with other third party applications and Systems(such as OpenTable's reservation platform) in order to identify theReceiver 106. For instance, Receiver 106 may be at a Fine Diningestablishment at which point Fulfillment System 160 would determinewhether to present the Pending Gift 153 at time of arrival, during thecourse of the meal, or upon payment.

Regarding Service Provider 164 delivery, if a service is selected by theGifter 104 (such as home cleaning or a babysitting service), theFulfillment System 160 may in tandem with Notification System 130coordinate that service directly with the Receiver 106 to ensure optimaltiming, execution and delivery, and to manage a service providerReservation System 133.

Regarding gift redemption, the Fulfillment System 160, in alignment withthe Insights Engine 140, may select a Content Provider 109 to use as thegift provider redeemed by the Receiver 106. In this instance, the Gifter104 has not selected a specific Content Provider 109 and instead relieson the Fulfillment System 160 to determine the Content Provider bestsuited for the Receiver 106 as exemplified in FIG. 6 and furtherexplained below.

Referring now to FIG. 12 , this figure is an exemplary table 1200illustrating User Sentiment Scores 1412 referenced in FIG. 1 accordingto one exemplary embodiment. As described above, information withinInsights Engine 140 is used throughout the first machine 104 giving agift, including notifications to second machines, receivers 106regarding redemption of gifts, and other touch points in which thesystem 100 interacts with a user as exemplified in FIGS. 3, 4, and 7-8and explained above.

The Insights Engine 140 may generate and store its own content, such asthrough the measurement of sentiment of the Receiver 106 through thecollection of data published to Social Media 146 and assign rankings toReceivers 106 based on the content that is published, as exemplified intable 1200, element ‘H’—User Sentiment Score. For instance, if oneReceiver 106 publishes words such “great”, “happy”, and “hooray” thenthey may be assigned a more positive sentiment ranking than a Receiver106 that uses words like “crummy”, “bad”, and “sad”—all of which wouldbe saved by the Moment Core module 101 to records stored in the UserProfile database 141 by Insights Engine 140 in a table 1200.

Table 1200 of FIG. 12 may exemplify how the Insights Engine 140 may ratea Gifter 104 and/or a Receiver 106 based on activity. Example inputsfrom channels a Gifter 104/Receiver 106 may interact with are,respectively, Facebook positive reaction (element ‘D’), Facebooknegative reaction (element ‘E’), SMS positive texts (element ‘F’), andMoment Network Platform (Moment Core module 101 running on server 99)(element ‘G’).

A Facebook positive reaction, specifically, may be a summary of apositive interactions from a Gifter 104/Receiver 106 on that platform.These positive attributes may indicate a post to the platform thatincludes the aforementioned positive content words (like “great” and“happy”), may include another individual “liking” a post, among otheractions a Gifter 104/Receiver 106 is able to make on that platform to bedeemed as indicating a more positive sentiment. Inversely, a Gifter104/Receiver 106 may also accumulate Facebook negative reactions, whichmay be a summation of negative reactions to a post to the platform,negative content being posted (like using words “crummy” and “bad”),among other actions that may be deemed as having a negative sentiment.

Both positive and negative content may originate from other platformsand applications Gifters 104/Receivers 106 provide Moment Core module101 access to. Content may also originate from a Gifter 104/User 106interactions with the Moment Network Platform (element ‘G’) itself,potentially accruing positive sentiment through the number of PendingGifts 153 sent, among other actions.

Table 1200 demonstrates at least three sample user sentiment scoringexamples. machine A (element ‘A’), in this case accrued 100 Facebookpositive reaction points, 20 Facebook negative reaction points, 50 SMSpositive texts points, and 50 Moment Network Platform points. In thissituation, machine A has a User Sentiment Score (here reflected aselement ‘AA’) that totals 180. This score is a tally of all positiveinteraction points, subtracted by any negative interaction points. So,machine A is shown to have 200 positive interaction points, with 20negative interaction points, resulting in the assigned User SentimentScore of 180 (element ‘AA’).

Machine B (element ‘B’) and Machine C (element ‘C’) are shown to haveUser Sentiment Scores, respectively, negative 120 (element ‘BB’) andpositive 60 (element ‘CC’). Potentially, the machine with the lowestsentiment score (in this case machine B with a negative 120 scoreassigned) may receive a notification through the Notification System 130of a Pending Gift 153 generated by the Gift System 150 with the goal tobrighten that day of that machine operator as the Insights Engine 140may determine an operator of a machine may benefit positively by arandom act of kindness. Or, the operator of this machine (also knownhere as machine B) may be suggested by Insights Engine 140 as apotential Receiver 106 as another Gifter 104 selects who to send a giftto.

Alternatively, machines ranked with higher User Sentiment Scores (inthis case machine A and machine C) may receive a notification throughthe Notification System 130 about their relative higher sentimentscores. These machines may receive a Pending Gift 153 to reinforce theirpositive sentiment scores, among other actions in which the InsightsEngine 140 may engage. Insights Engine 140 may filter Social Media 146to help determine a reason and timing to prompt that Gifter 104 to senda gift to a Receiver 106.

This information may be paired with information found within Calendars145 to determine frequency of interaction, important events, among othercontent saved by Insights Engine 140 to data in the User Profiledatabase 141. Insights Engine 140 may filter this data gathered, amongother accessible data (such as News and Pop Culture 1401) and serverecommendations to a Gifter 104 as described above and furtherexemplified in FIGS. 3, and 7-8 . To initiate sending a gift, the system100 may send a push notification via the Notification System 130 to apotential Gifter 104 to prompt the sending of a gift 153.

Referring now to FIG. 13 , this figure is a functional block diagram ofthe host computer Server 99 of FIG. 1 that can be used in the system 100and method for facilitating the transfer of a gift from a first machineto a second machine according to an exemplary embodiment of theinvention. The exemplary operating environment for the system 100 ofFIG. 1 includes a general-purpose computing device in the form of aconventional computer 99, 109, 130, 140, 160.

Generally, the computer 99 [referred to now as generally 99 but whichalso covers other servers/computers 109, 130, 140, and 160 of FIG. 1 ]includes a processing unit 1206, a system memory or storage 1208, and aSystem bus 1223 that couples various system components including thesystem memory 1208 to the processing unit 1206.

The system bus 1223 may be any of several types of bus structuresincluding a memory bus or memory controller, a peripheral bus, and alocal bus using any of a variety of bus architectures. The System memoryincludes a read-only memory (ROM) 1224 and a random access memory (RAM)1225. A basic input/output System (BIOS) 1226, containing the basicroutines that help to transfer information between elements withincomputer 99, such as during start-up, is stored in ROM 1224.

The computer 99 can include a hard disk drive 1227A for reading from andwriting to a hard disk, not shown, a universal serial bus (USB) drive1228 for reading from or writing to a removable USB flash memory unit1229, and an optical disk drive 1230 for reading from or writing to aremovable optical disk 1231 such as a CD-ROM or other optical media.Hard disk drive 1227A, USB drive 1228, and optical disk drive 1230 areconnected to System bus 1223 by a hard disk drive interface 1232, a USBdrive interface 1233, and an optical disk drive interface 1234,respectively.

Although the exemplary environment described herein employs hard disk1227A, USB drive 1229, and removable optical disk 1231, it should beappreciated by those skilled in the art that other types of computerreadable media which can store data that is accessible by a computer,such as magnetic cassettes, digital video disks (DVDs), Bernoullicartridges, RAMs, ROMs, and the like, may also be used in the exemplaryoperating environment without departing from the scope of the invention.Such uses of other forms of computer readable media besides the hardwareillustrated will be used in computer networked (i.e.—Internet) connecteddevices.

The drives and their associated computer readable media illustrated inFIG. 13 provide nonvolatile storage of computer-executable instructions,data structures, program modules, and other data for computer 99. Anumber of program modules may be stored on hard disk 1227, USB drive1229, optical disk 1231, ROM 1224, or RAM 1225, including, but notlimited to, an operating System 1235 and the Moment Core module(s) 101and User interface module 108 of FIG. 1 .

Program modules include routines, sub-routines, programs, objects,components, data structures, etc., which perform particular tasks orimplement particular abstract data types. A User may enter commands andinformation into computer 99 through input devices, such as a keyboard1240 and a pointing device 1242.

Pointing devices may include a mouse, a trackball, and an electronic penthat can be used in conjunction with an electronic tablet. Other inputdevices (not shown) may include a microphone, joystick, game pad,satellite dish, scanner, or the like. These and other input devices areoften connected to processing unit 106 through a serial port interface1246 that is coupled to the System bus 1223, but may be connected byother interfaces, such as a parallel port, game port, a universal serialbus (USB), Wi-Fi or the like.

The display 1247 may also be connected to System bus 1223 via aninterface, such as a video adapter 1248. As noted above, the display1247 can comprise any type of display devices such as a liquid crystaldisplay (LCD), a plasma display, an organic light-emitting diode (OLED)display, and a cathode ray tube (CRT) display.

A camera 1275 may also be connected to System bus 1223 via an interface,such as an adapter 1270. The camera 1275 can comprise a video camerasuch as a webcam. The camera 1275 can be a CCD (charge-coupled device)camera or a CMOS (complementary metal—oxide—semiconductor) camera. Inaddition to the monitor 1247 and camera 1275, the computer 100A mayinclude other peripheral output devices (not shown), such as speakersand printers.

The computer 99 may operate in a networked environment using logicalconnections to one or more remote computers 130 [or others in FIG. 1like 109, 140, and 160, just to name an exemplary few]. These remotecomputers 130 may comprise an Internet browser as illustrated in FIG. 13that is used to access the Moment Core module(s) 101. In such anexemplary scenario, the computers 99, 130 may comprise one or moreserver computers coupled together across the computer network 111.

Each remote computer 130 may also be another personal computer, acomputer Server, a mobile phone, a router, a network PC, a peer device,tablet (e.g., iPad) or other common network node. While the remotecomputer 130 typically includes many or all of the elements describedabove relative to the main computer 199, only a memory storage device1127B has been illustrated in this FIG. 13 for brevity. The logicalconnections depicted in FIG. 13 include a local area network (LAN) 111Aand a wide area network (WAN) 111B. Such networking environments arecommonplace in offices, enterprise-wide computer networks, intranets,and the Internet.

When used in a LAN networking environment, the computer 99 is oftenconnected to the local area network 111A through a network interface oradapter 1253. When used in a WAN networking environment, the computer 99typically includes a modem 1254 or other means for establishingcommunications over WAN 111B, such as the Internet. Modem 1254, whichmay be internal or external, is connected to system bus 1223 via serialport interface 1246. In a networked environment, program modulesdepicted relative to the main computer 99, or portions thereof, may bestored in the remote memory storage device 1227B of the remote computer130. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers 99 and 130 may be used.

Moreover, one of ordinary skill in the art will appreciate that thepresent invention may be implemented in other computer Systemconfigurations, including hand-held devices, multiprocessor Systems,microprocessor based or programmable consumer electronics, networkpersonal computers, minicomputers, tablets (e.g., iPad) mainframecomputers, and the like. The invention may also be practiced indistributed computing environments, where tasks are performed by remoteprocessing devices that are linked through a communications network. Ina distributed computing environment, program modules may be located inboth local and remote memory storage devices.

Referring to FIG. 14 , this figure is a diagram of an exemplary,non-limiting aspect of a portable computing device (PCD) 104, 105, 106—amachine—comprising a wireless mobile telephone, which corresponds withthose presented in the system 100 illustrated in FIG. 1 . In thisdescription, the terms “communication device,” “wireless device,”“wireless telephone,” “wireless communication device,” and “wirelesshandset” are used interchangeably. A portable computing device 104, 105,106 [generally as 104 from this point onward] could be a cellulartelephone, a pager, a PDA, a smartphone, a navigation device, or ahand-held computer with a wireless connection or link.

As shown, the mobile telephone 104 includes an on-chip System 1322 thatincludes a digital signal processor or a central processing unit 1324and an analog signal processor 1326 that are coupled together. Asillustrated in FIG. 14 , a display controller 1328 and a touchscreencontroller 1330 are coupled to the digital signal processor 1324. Atouchscreen display 1332 external to the on-chip System 1322 is coupledto the display controller 1328 and the touchscreen controller 1330.

FIG. 14 further illustrates a video encoder 1334, e.g., aphase-alternating line (“PAL”) encoder, a sequential couleur avecmemoire (“SECAM”) encoder, a national television System(s) committee(“NTSC”) encoder or any other video encoder, is coupled to the digitalsignal processor 1324. Further, a video amplifier 1336 is coupled to thevideo encoder 1334 and the touchscreen display 1332. A video port 1338is coupled to the video amplifier 1336. As depicted in FIG. 14 , auniversal serial bus (“USB”) controller 1340 is coupled to the digitalsignal processor 324. Also, a USB port 1342 is coupled to the USBcontroller 1340. A memory 112 and a subscriber identity module (“SIM”)card 1346 may also be coupled to the digital signal processor 1324.

Further, as shown in FIG. 14 , a digital camera 1348 may be coupled tothe digital signal processor 1324. In an exemplary aspect, the digitalcamera 1348 is a charge-coupled device (“CCD”) camera or a complementarymetal-oxide semiconductor (“CMOS”) camera.

As further illustrated in FIG. 14 , a stereo audio CODEC 1350 may becoupled to the analog signal processor 1326. Moreover, an audioamplifier 1352 may be coupled to the stereo audio CODEC 1350. In anexemplary aspect, a first stereo speaker 1354 and a second stereospeaker 1356 are coupled to the audio amplifier 1352. FIG. 14 shows thata microphone amplifier 1358 may be also coupled to the stereo audioCODEC 1350. Additionally, a microphone 1360 may be coupled to themicrophone amplifier 1358. In a particular aspect, a frequencymodulation (“FM”) radio tuner 1362 may be coupled to the stereo audioCODEC 1350. Also, an FM antenna 1364 is coupled to the FM radio tuner1362. Further, stereo headphones 1366 may be coupled to the stereo audioCODEC 1350.

FIG. 14 further illustrates a radio frequency (“RF”) transceiver 1368that may be coupled to the analog signal processor 1326. An RF switch1370 may be coupled to the RF transceiver 1368 and an RF antenna 1372.The RF transceiver 1368 may communicate with conventional communicationsnetworks as well as with global positioning System (“GPS”) satellites inorder to obtain GPS signals for geographical coordinates.

As shown in FIG. 14 , a keypad 1374 may be coupled to the analog signalprocessor 1326. Also, a mono headset with a microphone 1376 may becoupled to the analog signal processor 1326. Further, a vibrator device1378 may be coupled to the analog signal processor 1326. FIG. 14 alsoshows that a power supply 1380 may be coupled to the on-chip System1322. In a particular aspect, the power supply 1380 is a direct current(“DC”) power supply that provides power to the various components of themobile telephone 104 that require power. Further, in a particularaspect, the power supply is a rechargeable DC battery or a DC powersupply that is derived from an alternating current (“AC”) to DCtransformer that is connected to an AC power source.

FIG. 14 also shows that the mobile telephone 104 may include a momentcore application 107 [also shown in FIG. 1 ]. The moment coreapplication 107 may comprise hardware and/or software. The moment coreapplication 107 may communicate with the moment core module 101 of FIG.1 running on server 99.

As depicted in FIG. 14 , the touchscreen display 1332, the video port1338, the USB port 1342, the camera 1348, the first stereo speaker 1354,the second stereo speaker 1356, the microphone 1360, the FM antenna1364, the stereo headphones 1366, the RF switch 1370, the RF antenna1372, the keypad 1374, the mono headset 1376, the vibrator 1378, and thepower supply 1380 are external to the on-chip System 1322.

In a particular aspect, one or more of the method steps described herein(such as illustrated in FIGS. 2-6 ) may be stored in the memory 112 ascomputer program instructions, like the Moment Core module(s) 101. Theseinstructions may be executed by the digital signal processor or centralprocessing unit 1324, the analog signal processor 1326, or anotherprocessor, to perform the methods described herein. Further, theprocessors, 1324, 1326, the memory 112, the instructions stored therein,or a combination thereof may serve as a means for performing one or moreof the method steps described herein.

Referring now to FIG. 15 , this figure is an exemplary logical flowchart of a computer-implemented method 1500 for fulfilling a gift undercontrol of a first machine [i.e.—a gifter client device 104 of FIG. 1 ]and sending status of the gift to a second machine [i.e.—a receiverclient device 106 of FIG. 1 ] and where a Content Provider 109 sends arequest for one or more gifts to the Moment Core 101. Routine 1505 isthe first step/subprocess of method 1500.

In routine 1505, one or more gift(s)/moments are created and validatedas described above in connection with FIG. 1 and particularly, inconnection with database 175 of FIG. 1 . Routine 1505 may include themethod 300 of FIG. 3 described above. As mentioned above in connectionwith FIG. 3 , the system 100 via the Insights Engine 140 may suggestpotential receiver client devices 106. The gifter client device 104 mayselect one or more of the suggested receiver client devices 106 forsending one or more gift(s), and hence, create one or more “moments” forone or more receiver client devices 106.

Also in routine 1505, these gift(s) or moment(s) are validated andstored in database 175. As described above, validation of each giftwithin database 175 may include, but is not limited to, soft-touchchecks conducted by Moment Core 101 (i.e.—validating email address orzip codes associated with receiving client device 106) to deepvalidations where Moment Core 101 tries to interact with the receivingclient device 106 (i.e.—Send an email to the receiving device 106 andexpect an emailed response). These validated gift(s) are stored indatabase 175 and may be used by Moment Core 101 to match againstrequests made by content providers 109 for available gifts.

Next, after routine 1505, in step 1510, the gift(s) in database 175created by routine 1505 are published as “available.” In this step 1505,each record for a particular gift stored in database 175 may comprise aflag or status identifier. This flag may be set as “available” for beingincluded within a gift search. Alternatively, this flag may be set to“unavailable” if the gift has already been selected and is in theprocess of being fulfilled [i.e.—sent to the gifter client device 106]or has been fulfilled/been completed. When the status of the flag is setto “unavailable,” the gift is not included within any active search(es).

Subsequently, in step 1515, Moment Core 101 may receive one morerequest(s) for published available gifts(s) within database 175 thatmatch criteria that is provided in the one or more requests. Therequests for gifts may originate from one or more content providers 109.As note previously, Content Providers 109 comprise computer servers ofretailers (like Macy's, Target, Walmart, Amazon, Home Depot, Lowes,etc.), computer servers of service providers (like Merry Maids homecleaning), computer servers supporting digital media (like Netflix), andservers that may support other digital resources (like an emoji platformthat serves pictographs).

In this step 1515, the Content Providers 109 may send their requests forgifts over the computer network 111 via API 103 to Moment Core 101. Eachrequest may provide gift matching criteria such as, but not limited to,maximum value of gift, information known by the content provider 109about the receiving device 106, gift category, sales season/time ofyear, and an e-mail address of the receiving device 106, etc. This giftmatching criteria allows Moment Core 101 to search the database 175 inorder to apply the matching criteria as a filter to find one or morematching gifts/moments in database 175. The gift requests may be sentfrom Content Providers 109 at various times and/or based on varyingconditions.

Each Content Provider 109 may track when a receiver device 106 hasentered into a physical store and/or is in close proximity to theContent Provider 109. The Content Provider 109 may track a receiverdevice 106 as part of its application software that may be running on arespective receiver device 106. The application software for a ContentProvider 109 may have access to location data that is stored within thereceiver device 106.

Alternatively, a Content Provider 109 may detect a receiver device 106via a Wi-Fi signal; location services; a scan of a QR code; by a creditor loyalty card swipe at check out; a store representative (i.e.receiver device 106 moves through door, store representative asksreceiver device 106 for membership number, and then proceeds to check-inreceiver device via a tablet owned by the Content Provider 109); and areceiver device 106 may be detected on a video camera and image matchedto an account, etc.

A first Content Provider 109 may send gift requests just prior to areceiver device 106 trying to pay for goods and/or services from thefirst Content Provider 109, such as the receiver device 106 logging intoapplication software of the first Content Provider 109 and indicatingthat check-out is needed. Alternatively, a second Content Provider 109may send its gift requests once payment transaction processing hasinitiated, such as when the receiver device 106 has selected the type ofpayment to complete a goods and/or services purchase transaction [i.e.credit card or cash is selected as the form of payment by the receiverdevice 106].

A Content Provider 109, such as a hardware retailer, may provide ane-mail address of a receiver device 106 that the Content Provider 109has detected to be present within a particular store location. TheContent Provider 109, here a hardware retailer, may also provide dataindicating a time of year associated with sales, such as the MemorialDay holiday. The Memorial Day holiday is known in the United States asthe usual holiday that “kicks-off”/starts the summer months in theUnited States.

Next, in step 1520, the Moment Core 101 may filter published availablegifts within database 175 based on the matching criteria provided in theone or more gift requests received via API 103 and the computercommunications network 103 from the content providers 109. In this step1520, the Moment Core 101 may use the Insights Engine 140 and other datarelated to the current matching criteria to assist in strengthening thepositivity of a match within the gift database 175.

For example, the Moment Core 101 may relay the e-mail address of thereceiving device 106 to the Insights Engine 140 provided in the requestto conduct a search of user profiles of the System 101 in order to finda matching user matching the e-mail address of the gift request. If amatching user of System 101 is found by the Insights Engine 140, theInsights Engine 140 may add to the matching criteria additional giftparameters taken from the matching user profile. For example, supposethe matching user profile lists a preference of enjoying being outdoorsand a preference for cooking.

The Moment Core 101 may also relay the other parameter in this exemplaryrequest search sent to the Insights Engine 140. The other parameter isan upcoming holiday, such as the Memorial Day Holiday celebrated in theUnited States. The Insights Engine 140 may check with the News and PopCulture Server 1401 to learn that the Memorial Day Holiday is associatedwith cook-outs/outdoor cooking and grills. The Insights Engine 140 maythen match the cooking preference in the user profile with grills. TheInsights Engine 140 may then relay the cooking preference of the userfrom the user's profile and grills associated with news/pop culture tothe Moment Core 101. The Moment Core 101 may add these two parameters,cooking preference and grills, to the search inquiry. Thus, the searchinquiry/request now includes at least the following five parameters: (a)e-mail address of receiver device 106 from the Content Provider 109, (b)an outdoors preference from the profile of the receiver device 106, (c)a cooking preference from the profile of the receiver device 106, (d)the Memorial Day Holiday from the Content Provider 109, and (e) grillsfrom the Insights Engine 140.

The Moment Core then filters the gift database 175 by applying the fiveparameters (a-e) against gifts marked as available in the gift database175. Suppose that the gifter device 104 created a first gift forreceiving device 106 and it was published as available in the giftdatabase 175. Also suppose the gift had a type parameter of “cooking”and had a value range parameter of between about $200.00 (U.S. Dollars)and about $300.00 (U.S. Dollars).

It is noted that while U.S. currency is referenced in thisspecification, it is recognized that other currencies may be used inother jurisdictions as appropriate and as understood by one of ordinaryskill in the art. Also, alternative currencies besides government issuedcurrencies are possible such as digital currency, like BitCoin as ofthis writing.

The Moment Core 101 would find a match with the e-mail address [ContentProvider parameter (a)]; and the “cooking” parameter of the gift and the“cooking preference” parameter (c) from the user profile for thereceiving device 106 found by the Insights Engine 140. Suppose thegifter device 104 created a second gift for the receiving device 106 andthis second gift had the additional parameter of swimming.

For this second gift, based on the search criteria/parameters (a thrue), at least one match based on the e-mail address would exist betweenthe gift database 175 and the search criteria. The Moment Core 101 wouldthen create a filtered list or matching list that isordered/sequenced/prioritized based on a degree in match. In thisscenario, the first gift would be designated with a higher match valuecompared to the second gift since at least two search parameters matchthe first gift [at least search criteria (a) and (e) for the first gift]while only one search parameter may match the second gift [single searchcriteria (a)=e-mail address of receiving device.]

Next, in decision step 1525, the Moment Core 101 would then determinewhich one or more gifts it should send to the Content Provider 109.Thus, for at least one match, the “Yes” branch would then be followed tosteps 1530 and 1535. If the inquiry to decision step 1525 is negative,meaning that no matches in the database 175 were found by the MomentCore, then the “No” branch would then be followed in which the method1500 would return back to the first step 1505.

The matching first gift would be identified by the Moment Core with thefollowing parameters: (a) the e-mail address of receiver device 106 fromthe Content Provider 109; (e) grills from the Insights Engine 140; and(f) a gift value of between $ about $200.00 (U.S. Dollars) and about$300.00 (U.S. Dollars) which was part of the parameters of the publishedgift in the gift database 175.

Steps 1530 and 1535 flow from the “Yes” branch of decision step 1525.This means that these steps and their succeeding steps may be performedin parallel as understood by one of ordinary skill in the art. In step1530, the Moment Core 101 may change the status identifier or flag forthe gift from “available” to—reserved—while the gift is being fulfilled.Note that this status change may not be permanent since it is possiblefor the fulfillment system 160 of a Content Provider 109 to not be ableto fulfill/complete a gift as will be described below.

If another search is initiated by the same Content Provider 109 or adifferent Content provider 109, the—reserved—status will prevent thecurrent gift [i.e. the cooking gift in this example] from being includedwithin any subsequent gift searches while the current gift is beingprocessed.

Referring now to step 1535, which may be performed in parallel with step1530 as noted above, in this step the Moment Core 101 may transmit theone or more gift(s) from the search query via API 103 and the computercommunications network 111 to the one or more Content Providers 109.Next, in step 1555, each Content Provider 109 may transmit the gift(s)from the search to the one or more Fulfillment Systems 160.

In decision step 1560, a Fulfillment System 160 may determine if thereceived gift from Moment Core 101 search inquiry can befulfilled/completed. If the inquiry to decision step 1560 is negative,then the “No” branch may be followed to step 1565 in which theFulfillment System 160 releases the gift(s) and transmits this status toMoment Core 101 via the computer communication network 111 and API 103.The Fulfillment System 160 may determine that one or more gifts cannotbe fulfilled for various reasons and/or conditions.

For example, in the grill example, a particular grill matching the priceof the gift request may be out-of-stock. As another non-limitingexample, the receiver device 106 may be about to complete payment andcancels the payment transaction (i.e.—“I don't want this,” or justleaves the store/proximity of the Content Provider 109 before completingthe payment transaction).

As another example of a gift not being fulfilled by the FulfillmentSystem 160, technical issues may exist at the Content Provider 109.Suppose the gift is only one of several products that are about to bepurchased by the receiver device 106. Suppose the Content Provider 109cannot process a credit card transaction so that the entire purchasetransaction, that now includes the gift of the grill, has to be rolledback/terminated.

Step 1550 follows step 1565 in which Moment Core 101 now changes thegift status from—reserve—to available. Referring back to decision step1560, if the inquiry to decision step 1560 is positive, meaning that theFulfillment System 109 can complete/fulfill the gift, then the “Yes”branch is followed to step 1570.

In step 1570, the Fulfillment System 109 may complete the gift byproviding it to the receiver device 106. In the grill example, the boxcontaining the new grill may be removed from inventory and a bar code onthe box may be scanned at the check-out for pick-up by the receivingdevice 106. The scan of the bar code at the check-out may trigger theFulfillment System 109 to send a “gift complete” message via thecomputer communications network 111 and API 103 to Moment Core.

Next, in step 1575, upon receiving the “gift complete” message from theFulfillment System 109, the Moment Core 101 may utilize the NotificationSystem 130 to notify the receiver device 106 about the gift. The MomentCore 101 may also allow the receiver device 106 the opportunity torespond to the gifter device 104 (i.e.—a text-based message, photo,video, or any combination of.)

Also, in step 1575, the Notification System 130 may generate one or moremessages like the messages illustrated in FIGS. 8A-8C. So for the grillexample gift, one of the screen shots, like screen shot 1023 of FIG. 8Cmay be modified to show that the grill was a gift sent by the gifterdevice 104. FIG. 16 illustrates a screen shot 1600 that provides animage 1610 of the grill model which was provided as the gift to thereceiver device 106. A message 1605 may be provided on the display aswell indicating the owner of the gifting device 104 and describing whenthe gift was fulfilled by the Content Provider 109. After step 1575, themethod 1500 returns back to step 1505 described above.

Referring back to step 1530, which may be performed in parallel withstep 1535 as noted above, in this step the Moment Core 101 changed thestatus of matching published gift(s) from the “available” status toa—reserved—status. Subsequently, in step 1540, the Moment Core 101 maydetermine status of gift reservation(s)—those gifts forwarded to theContent Providers 109—based on one or more rules.

For example, one rule may comprise a timer where the Moment Core 101will allow a reserved gift to remain in the—reserved—status for a finiteperiod of time, such as, but not limited to, on the order of hundreds ofseconds to several minutes. Another rule may include one where MomentCore 101 calls on an API for a server of a Content Provider 109 toconfirm communication connectivity or a computer connection (i.e.Internet connection) “still working” message.

One or more other rules may check for acts of fraud or potential fraud.For example, one rule may determine if duplicate requests for giftscontain the same matching criteria but from two different locations.Suppose a gift exists for $20 in the gift database 175 and has metadataof “e-mail=jdoe@gmail.com”. In other words, a Content Provider 109providing this e-mail address will be matched to this $20 gift/moment.Suppose a Content Provider 109 starts a checkout process forjdoe@gmail.com using a loyalty card (i.e.—this e-mail address may be inthe mag-stripe data).

The Moment Core 101 would receive the API request from Content Provider109 and make a match based on the e-mail address, and then “reserve” the$20 Moment/Gift for the Content Provider's usage at the locationoriginating the gift request. Now it turns out that some fraudstercloned the loyalty card and tries to make a purchase during the sametime window as the real John Doe (which is currently reserved by theContent Provider 109 originating the legitimate gift request).

This potentially fraudulent event, which may be characterized as the“same person cannot be in same place at same time” rule is a goodindicator that fraudulent activity may be occurring or at least it is anevent that should be stopped and analyzed to understand why happened.Other rules are possible and are within the scope of this disclosure asunderstood by one of ordinary skill in the art.

Next, in decision step 1545, the Moment Core 101 may check the status ofthe one or more rules described above. If a reserved gift does not matcha condition of any of the rules, which is a negative result for thisinquiry, then the “No” branch is followed back to step 1540 where thestatus of one or more rules that may be executed in parallel arecontinuously checked by the Moment Core 101.

If the inquiry to decision step 1545 is positive, meaning that areserved gift matches the conditions of one or more rules, then the“Yes” branch is followed to step 1550 which was briefly described above.In this step 1550, the reserved gift status is now changed back to the“available” status and published in the database 175 with this updatedstatus so that the gift may now be part of a subsequent gift search. Theupdate to the reserved gift status will be changed to a value based onthe rule that was triggered.

For example, a timeout rule would result in a status going back to“available” but if there was a fraud detection rule triggered than thestatus would be updated to “fraud.” Status such as “fraud” may triggernotifications to Moment support staff to conduct further research beforeputting the reserved gift status back into circulation [i.e. puttingback to the “available” status]. In this step 1550, the Moment Core 101may transmit this updated status via API 103 and the computercommunications network to the Fulfillment System 160.

The receipt of this change in status of the gift from the reservedstatus to the “available” status may trigger decision step 1560 and anegative inquiry to that step. This means it is not possible to fulfillthis gift now with this change in status from reserved to “available”status by the Moment Core 101. The method 1500 then returns to the firststep 1505 of the method 1500.

Certain steps in the processes or process flows described in thisspecification naturally precede others for the invention to function asdescribed. However, the invention is not limited to the order of thesteps described if such order or sequence does not alter thefunctionality of the invention. That is, it is recognized that somesteps may be performed before, after, or parallel (substantiallysimultaneously with) other steps without departing from the scope andspirit of the invention. Further, words such and “thereafter”, “then”,“next”, etc. are not intended to limit the order of the steps. Thesewords are simply used to guide the reader through the description of theexemplary method.

Additionally, one of ordinary skill in programming is able to writecomputer code or identify appropriate hardware and/or circuits toimplement the disclosed invention without difficulty based on the flowcharts and associated description in this specification.

Therefore, disclosure of a particular set of program code instructionsor detailed hardware devices is not considered necessary for an adequateunderstanding of how to make and use the invention. The inventivefunctionality of the claimed computer implemented process is explainedin more detail in the above description and in conjunction with thefigures that may illustrate various processes flows.

In one or more exemplary aspects, the functions described may beimplemented in hardware, software, firmware, or any combination thereof.If implemented in software, the functions may be stored on ortransmitted as one or more instructions or code on a computer-readablemedium. Computer-readable media include both storage media andcommunication media including any medium that facilitates transfer of acomputer program from one place to another. A storage media may be anyavailable media that may be accessed by a computer. By way of example,and not limitation, such computer-readable media may comprise RAM, ROM,EEPROM, CD-ROM, Flash, or other optical disk storage, magnetic diskstorage or other magnetic storage devices, or any other medium that maybe used to carry or store desired program code in the form ofinstructions or data structures and that may be accessed by a computer.

Also, any connection is properly termed a computer-readable medium. Forexample, if the software is transmitted from a website, Server, or otherremote source, such as in “cloud” computing, using a coaxial cable,fiber optic cable, twisted pair, digital subscriber line (“DSL”), orwireless technologies such as infrared, radio, and microwave, then thecoaxial cable, fiber optic cable, twisted pair, DSL, or wirelesstechnologies such as infrared, radio, and microwave are included in thedefinition of medium.

Disk and disc, as used herein, includes compact disc (“CD”), laser disc,optical disc, digital versatile disc (“DVD”), floppy disk, and blue-raydisc where disks usually reproduce data magnetically, while discsreproduce data optically with lasers. Combinations of the above shouldalso be included within the scope or computer-readable media.

Alternative embodiments for the system and method of the presentdisclosure will become apparent to one of ordinary skill in the art towhich the invention pertains without departing from its spirit andscope. Therefore, although selected aspects have been illustrated anddescribed in detail, it will be understood that various substitutionsand alterations may be made therein without departing from the spiritand scope of the present invention, as defined by the following claims.

What is claimed is:
 1. A computer-implemented method for facilitatingsending of a gift from a first machine to a second machine, thecomputer-implemented method comprising: a processor of a giftingcomputer server creating a gifts database of gifts associated withcontacts of the first machine, the processor of the gifting computerserver identifying gifts desired by a profile associated with the secondmachine by accessing an on-line store database containing at least oneof products and services that were selected by the second machine for awish list, the identified gifts comprising at least one of products,services, and gift categories; displaying the identified gifts on adisplay device of the first machine; receiving with the processor of thegifting computer server a selection of gifts from the first machinebased on the identified gifts displayed on the display device of thefirst machine; a processor of the gifting computer server identifyingthe selected gifts as available for searching; a processor of a locatingsystem automatically detecting a presence of the second machine in acheck-out lane of a content provider, the locating system sending apresence message indicating the presence of the second machine withinthe check-out lane to a content provider computer server; a processor ofthe gifting computer server receiving from a computer communicationsnetwork a request for a gift to be sent to the second machine, therequest originating from the content provider computer server, therequest being generated by the content provider computer server inresponse to the presence message from the locating system indicating thepresence of the second machine within the check-out lane, the requestincluding criteria generated by the content provider computer serverthat received the presence message from the locating system; a processorof the gifting computer server searching and filtering the giftsdatabase based on the criteria from the content provider computer serverthat is part of the request for the gift; a processor of the giftingcomputer server determining if one or more gifts match the criteriabased on the criteria; a processor of the content provider computerserver verifying that at least one gift that matches the criteria willbe fulfilled by the content provider and generating a fulfillmentmessage describing the at least one gift which will be fulfilled by thecontent provider; a processor of a computer server transmitting a firstgift complete message over the computer communications network to thefirst machine and transmitting a second gift complete message over thecomputer communications network to the second machine, the first andsecond gift complete messages comprising information indicating that atleast one gift that matches the criteria is being fulfilled by thecontent provider; the first machine receiving the first gift completemessage from the computer communications network; the first machinedisplaying the first gift complete message in a graphical userinterface, the first gift complete message comprising an image of the atleast one gift that matches the criteria, the first gift completemessage further comprising text describing the at least one gift and anidentity of the content provider which fulfilled the at least one gift;and the second machine receiving the second gift complete message fromthe computer communications network.
 2. The method of claim 1, furthercomprising a processor of the gifting computer server changing one ormore gifts that match the criteria to a reserved status.
 3. The methodof claim 1, further comprising a processor of the gifting computerserver transmitting the one or more gifts that match the criteria over acomputer communications network to the content provider computer server.4. The method of claim 1, further comprising a processor of the giftingcomputer server receiving the fulfillment message from the computercommunications network that at least one gift that matches the criteriawill be fulfilled by the content provider.
 5. The method of claim 1,further comprising the second machine displaying the second giftcomplete message in a graphical user interface, the second gift completemessage comprising an image of the at least one gift that matches thecriteria.
 6. The method of claim 5, wherein the second gift completemessage further comprises text describing the at least one gift in theimage and a name of a person associated with the first machine whichauthorized the at least one gift from the gifting computer server. 7.The method of claim 1, further comprising: a processor of a computerserver determining a status of the one or more gifts that match thecriteria that were sent over the computer communications network basedon one or more rules; and a processor of a computer server determiningif the status of any of the one or more gifts matches one or more rules.8. The method of claim 7, further comprising: a processor of a computerserver changing a reserved status for a gift in the gifts database to anavailable status if the gift matches one or more rules.
 9. The method ofclaim 1, wherein the first machine and second machine comprise portablecomputing devices.
 10. The method of claim 9, wherein the portablecomputing devices comprise at least one of battery-powered hand-helddevices.
 11. A computer system for facilitating sending of a gift from afirst hand-held machine to a second hand-held machine, thecomputer-implemented method comprising: a locating system automaticallydetecting a presence of the second hand-held machine in a check-out laneof a content provider, the locating system sending a presence messageindicating the presence of the second hand-held machine within thecheck-out lane to a content provider computer server; a gifting computerserver creating a gifts database of gifts associated with contacts ofthe first hand-held machine; the gifting computer server identifying thegifts as available for searching, the gifting computer serveridentifying gifts desired by a profile associated with the secondmachine by accessing an on-line store database containing at least oneof products and services that were selected by the second machine for awish list, the identified gifts comprising at least one of products,services, and gift categories; the identified gifts being displayed on adisplay device of the first hand-held machine; the gifting computerserver receiving a selection of gifts from the first hand-held machinebased on the identified gifts displayed on the display device of thefirst hand-held machine; the gifting computer server receiving from acomputer communications network a request for a gift to be sent to thesecond hand-held machine, the request originating from the contentprovider computer server and being generated by the content providercomputer server in response to the presence message from the locatingsystem indicating the presence of the second machine within thecheck-out lane, the request including criteria generated by the contentprovider computer server that received the presence message from thelocating system; the gifting computer server searching and filtering thegifts database based on the criteria from the content provider computerserver that is part of the request for the gift; the gifting computerserver determining if one or more gifts match the criteria based on thecriteria; the content provider computer server verifying that at leastone gift that matches the criteria will be fulfilled by the contentprovider and generating a fulfillment message describing the at leastone gift which will be fulfilled by the content provider; and thegifting computer server transmitting a first gift complete message overthe computer communications network to the first hand-held machine andtransmitting a second gift complete message over the computercommunications network to the second hand-held machine, the first andsecond gift complete messages comprising information indicating that atleast one gift that matches the criteria is being fulfilled by thecontent provider computer server; the first machine receiving the firstgift complete message from the computer communications network; thefirst machine displaying the first gift complete message in a graphicaluser interface, the first gift complete message comprising an image ofthe at least one gift that matches the criteria, the first gift completemessage further comprising text describing the at least one gift and anidentity of the content provider which fulfilled the at least one gift;and the second machine receiving the second gift complete message fromthe computer communications network.
 12. The system of claim 11, whereinthe gifting computer server changes one or more gifts that match thecriteria to a reserved status.
 13. The system of claim 11, wherein thegifting computer server transmits the one or more gifts that match thecriteria over a computer communications network to the content providercomputer server.
 14. The system of claim 11, wherein the giftingcomputer server receives a fulfillment message from the computercommunications network that at least one gift that matches the criteriawill be fulfilled by the content provider computer server.
 15. Thesystem of claim 11, wherein the second machine displays the second giftcomplete message in a graphical user interface, the second gift completemessage comprising an image of the at least one gift that matches thecriteria.
 16. The system of claim 15, wherein the second gift completemessage further comprises text describing the at least one gift in theimage and a name of a person associated with the first machine whichauthorized the at least one gift from the gifting computer server. 17.The system of claim 11, wherein the gifting computer server determines astatus of the one or more gifts that match the criteria that were sentover the computer communications network based on one or more rules; andthe gifting computer server determining if the status of any of the oneor more gifts matches one or more rules.
 18. The system of claim 11,wherein the gifting computer server changes a reserved status for a giftin the gifts database to an available status if the gift matches one ormore rules.
 19. The system of claim 11, wherein the first hand-heldmachine and second hand-held machine comprise portable computingdevices.
 20. The system of claim 19, wherein the portable computingdevices comprise at least one of battery-powered hand-held devices.